Summary
When using Terraform to set up Airbyte connections from RDS MySQL to BigQuery, the non_breaking_schema_updates_behavior is set to ignore by default. However, when columns are added or removed, Airbyte deletes the existing table and creates a new one without the dropped column or with the new column. The user did not receive any notifications despite setting them up. Seeking help to understand why this behavior occurred and if others have experienced similar issues.
Question
Hi, I’m using terraform to set up my Airbyte connections from RDS MySQL to BigQuery. I didn’t set non_breaking_schema_updates_behavior, and the https://registry.terraform.io/providers/airbytehq/airbyte/latest/docs/resources/connection#non_breaking_schema_updates_behavior|default is ignore. But when columns get removed or added, Airbyte deleted the existing table and created a new one without the dropped column/with the new column. There was no notification for it even though I set all notifications that I could in the overall settings page (except for successful syncs) and in each connector. Could anyone help me understand why this happened? Have you experienced anything similar?
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.