I set up a connection to transfer tables from Bigquery to MySQL. I need it for a one-time / adhoc transfer of the full dataset. Anyways, when it synced, I noticed two undesirable side effects that I was hoping to avoid in my ETLs: • bunch of new tables in the destination that mirror source table, but start with _ airbyte...._ (starting with undersore). ◦ I don't want any extra tables in my destination, or at least I would have preferred to have been warned about this in the UI • bunch of airbyte's operational extra columns in every destination tables with underscores. ◦ Again, I do not not need this and would prefer to have been warned about this in the UI (The sync job ran 30 min) Anyways, now that I know how Airbyte does the sync, I was wondering if there are options to turn off these extra tables and columns? (I'm basically looking for an adhoc replication solution that keeps the schemas as is. If all these extras are created to track incremental changes, and there is no way around this using Airbyte – how do I find the right solution elsewhere? Thank you!!)

Sorry @Nikolay Kulmatitskiy, I seem to be having a bit of trouble. Don't worry though, I've pinged my support folks and they will try to fix me up! 🧑‍💻 Perhaps try again in 5mins?

Can you try now