Summary
After upgrading Redshift destination to 2.6.4 and MySQL source to 3.4.7, full refresh overwrite syncs result in 0 rows in the destination table when there are no changes in the source table. The first sync after a reset works, but subsequent syncs fail. Downgrading the Redshift connector is not resolving the issue.
Question
Hi Team! Since upgrading my Redshift destination to 2.6.4 and my MySQL source to 3.4.7 full refresh overwrite syncs results in 0 rows in the destination table if there were no changes in the source table. The first sync after a reset works successfully, but following syncs will be faulty. I am on Airbyte 0.53.1. There is this github issue that is encountering the same issue when using postgres as data source: https://github.com/airbytehq/airbyte/issues/39039. I am floating right now since downgrading the Redshift connector is not working for me. It’s resetting for hours and has not finished.
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.