@kapa.ai I'm trying to create a connection between Redshift source and destination. Both targets were created successfully but when I try to create the connection, I'm receiving the following error: Discovering schema failed Something went wrong in the connector. See the logs for more details.

Based on the information provided in the knowledge sources, it appears that you're encountering a known issue with the Redshift source connector in Airbyte. This problem has been reported by several users and is related to schema discovery failures. Here's what we know: 1. The issue seems to be present in newer versions of the Redshift source connector. Specifically, versions 0.3.12 and above have been reported to have this problem [Source Redshift - error trying to get schema from the source (Since version 0.3.12) · Issue #17988 · airbytehq/airbyte · GitHub](https://github.com/airbytehq/airbyte/issues/17988). 2. One user reported that reverting to version 0.3.7 of the Redshift source connector resolved the issue [Redshift Source Discovering schema failed](https://discuss.airbyte.io/t/2979). 3. The error message you're seeing is consistent with what others have reported, indicating a problem during the schema discovery phase. To troubleshoot this issue, you could try the following steps: 1. Check the version of your Redshift source connector. If it's 0.3.12 or above, consider downgrading to version 0.3.7 to see if that resolves the issue. 2. Examine the detailed logs of your Airbyte instance. The error message suggests that more information might be available in the logs. 3. Ensure that the user you're using to connect to Redshift has the necessary permissions to read schema information. 4. If possible, try creating a test user with access to only one table and see if the schema discovery works for that limited scope. If the problem persists, you may want to report this issue to the Airbyte team, providing them with your specific configuration details and log information. They are aware of this problem and may have additional troubleshooting steps or a fix in the works.

Based on the error message and stack trace you've provided, it appears you're encountering a known issue with the Redshift source connector in Airbyte. This error occurs during the schema discovery process and is related to handling null values in column metadata. Let me provide some insights based on the available information: 1. This issue has been reported and discussed in several Airbyte GitHub issues, including [Issue #25825](https://github.com/airbytehq/airbyte/issues/25825) and [Issue #19911](https://github.com/airbytehq/airbyte/issues/19911). 2. The error typically occurs when there are views with no schema binding in your Redshift database. As mentioned in one of the issues: "When the schema contains at least one view 'with no schema binding', then the precondition scan fails with a NPE. This also happens when tables/views from a schema were synched successfully with airbyte, and that view is newly added to the schema, effectively breaking that connection during next pre-scan." 3. A potential workaround mentioned is to only use Airbyte on schemas that don't contain any views with no schema binding. 4. It's worth noting that this issue has been present in multiple versions of the Redshift source connector. Some users have reported success with older versions, such as version 0.3.7, as mentioned in a [forum post](https://discuss.airbyte.io/t/2979). 5. The development team has been aware of this issue, and there have been attempts to fix it. However, it seems the problem persists in some scenarios. To troubleshoot and potentially resolve this issue, you could try the following: 1. Check if you have any views with no schema binding in your Redshift database and consider removing them or binding them to a schema. 2. Try using an older version of the Redshift source connector, such as 0.3.7, if possible. 3. If the issue persists, it would be helpful to report it on the Airbyte GitHub repository with details about your specific setup and schema. 4. Keep an eye on updates to the Redshift source connector, as the development team may release a fix for this issue in future versions. If none of these suggestions work, you may need to wait for a more comprehensive fix from the Airbyte team. In the meantime, you could consider using a different method to extract data from Redshift if this is blocking your workflow.

@kapa.ai Downgrading to version 0.3.7 works for me, thanks.

A message from kapa.ai

New message text here