Destination-redshift 0.3.32 issues with SUPER data type

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: EC2 t2.large
  • Memory / Disk:
  • Deployment: Docker
  • Airbyte Version: 0.36.2-alpha
  • Source name/version: google-analytics 0.1.19
  • Destination name/version: redshift 0.3.32
  • Step: Sync
  • Description:

When loading to S3 prior to copying to redshift, airbyte is erroring out (specific operation below, logs attached). Downgrading to 0.3.28 resolves the issue. And, interestingly enough, performing the same sync without first copying to S3 (e.g., just INSERTing to redshift) works on 0.3.32.

2022-04-28 16:03:43 destination > 2022-04-28 16:03:43 INFO i.a.i.d.r.RedshiftSqlOperations(onDestinationCloseOperations):110 - Executing operations for Redshift Destination DB engine...
2022-04-28 16:03:43 destination > 2022-04-28 16:03:43 INFO i.a.i.d.r.RedshiftSqlOperations(discoverNotSuperTables):129 - Discovering NOT SUPER table types...
2022-04-28 16:03:43 destination > 2022-04-28 16:03:43 ERROR i.a.i.d.r.RedshiftSqlOperations(discoverNotSuperTables):146 - Error during discoverNotSuperTables() appears: 
2022-04-28 16:03:43 destination > java.sql.SQLException: [Amazon](500310) Invalid operation: syntax error at or near "null" 

logs-2275.txt (95.7 KB)

There is an issue to solve the problems with latest version of Redshift @davidfromtandym you can subscribe to the issue to receive updates: All Syncs with redshift destination 0.3.32 fail rollback to version 0.3.28 resolves the issue · Issue #12265 · airbytehq/airbyte · GitHub

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.