Hi all. I'm a new user of Airbyte cloud, I will be...
# replication-troubleshooting
g
Hi all. I'm a new user of Airbyte cloud, I will be syncing AWS Aurora MySQL tables to BigQuery, using CDC replication method. I have a question about schema changes. In the docs, I read
We do not support schema changes automatically for CDC sources. We recommend resetting and resyncing data if you make a schema change
I have 2 questions: • If a field is added in one of the source tables, is this going to break the sync? Or it is merely going to be ignored? • Is there a plan to make Airbyte handle somehow MySQL schema changes? (I found this github issue, but there are no updates) Thank you!
šŸ™ 2
To kind of answer my question, there is already a topic about it in the forums, see here. It seems that the connection will not break and fields are treated as optional. But on the other hand, to update the schema one has to reset the connection.. This is not an efficient solution, but they seem to be working on it: https://app.harvestr.io/roadmap/view/pQU6gdCyc/airbyte-roadmap?p=bj4hNcr3h
u
Hello Giorgos Tzanakis, it's been a while without an update from us. Are you still having problems or did you find a solution?
g
Hi Sajarin, thanks a lot for the reply. It would be very helpful if somebody could answer my first question: • If a field is added in one of the source tables, is this going to break the sync? Or it is merely going to be ignored? My educated guess is that it would be the latter, but it would be extremely helpful if somebody could confirm, as we are planning our budget for airbyte cloud.
u
Hey Giorgos, I believe that the sync won't break but will require a resync of the data (similar to a migration) as you already pointed out earlier. This is not an efficient solution but we hope to be able to solve this issue in accordance with our roadmap. Let us know if you have more questions and apologies for the long delay in the answer here šŸ™‚
g
Thanks for getting back to me on this, @Sajarin Dider , good to know