- Is this your first time deploying Airbyte?: Yes
- OS Version / Instance: MacOS
- Deployment: Local via docker-compose
- Airbyte Version: What version are you using now?
- Source name/version: Postgres/13.3
- Destination name/version: Postgres/14.2
- Step: The issue is observed during syncs of the Connection.
I am working with Airbyte locally through the provided Docker files and local setup documentation. I was interested in evaluating how the Postgres CDC operated, so I set up a Postgres to Postgres (through two additional Docker containers running the respective Postgres versions noted above) Connection in Airbyte.
One particular feature that is important for my use case is handling schema changes in the source and how to reflect in the target or destination. The Airbyte documentation seems to suggest that, even though schema changes cannot be detected automatically, that I should reset and resync the data through the expected flow conducted via the UI or similar.
However, upon attempting to do so, I find that I am unable to reflect column additions (further DDL changes such as column deletions were not evaluated yet) from the source in the target even when resetting and resyncing the data for a Connection.
The sync does not fail; the data is captured but the destination does not capture any new columns unless I apply one of two workarounds I’ve been able to use thus far:
- Completely set up a new Connection, specifically with a newly defined Source, so that the schema of the tables is re-inspected
- Manually update the
catalogfield for the Connection in the
connectionby connecting to the Airbyte meta DB directly and making the change.
Neither of these feels like the ideal flow to me. I thought at this point I would turn to the Airbyte community and ask how I should be approaching schema changes in a Postgres Source so that syncs can flow data as expected to a destination?
Any help or guidance on this topic would be much appreciated!