Summary
Error message ‘Internal Server Error: Cannot invoke AirbyteCatalog.getStreams() because discovered is null’ after making a small tweak to a connector built with CDK. User is seeking guidance on how to fix this issue.
Question
<@U04SE163WC8> I made a small tweak to a connector built with the CDK, and now I’m getting the error below. how can i fix this?
Internal Server Error: Cannot invoke "io.airbyte.api.model.generated.AirbyteCatalog.getStreams()" because "discovered" is null
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.
Join the conversation on Slack
["error", "airbytecatalog", "cdk-connector", "tweak"]
The error message you’re seeing suggests that the discovered object is null when the getStreams() method is invoked. This could be due to a variety of reasons, such as a problem with the connector’s discovery process or a misconfiguration. Unfortunately, the information provided in the extracts does not include a specific solution to this error. However, here are a few general troubleshooting steps you can take: 1. Check your connector’s discovery process: Ensure that your connector’s discovery process is correctly identifying the available streams. The discovery process is responsible for populating the discovered object. 2. Review your connector’s configuration: Make sure that your connector is correctly configured. Misconfigurations could lead to unexpected null values. 3. Debug your connector: If the error persists, you may need to debug your connector to identify where the null value is coming from. This could involve adding logging statements, running the connector in a debugger, or other debugging techniques. If you continue to experience issues, I recommend reaching out to the Airbyte community on their forum or GitHub for more specific assistance.