@kapa.ai I have a connection from mysql to snowflake, that was previously using just the raw tables (ie, "disable final tables" enabled in the snowflake destination connector config). Can/how do I upgrade the connection to direct-load?

Upgrading a Raw-Tables-Only Connection to Direct-Load (Snowflake 4.0.0) Yes, you can upgrade, but there are some important steps and caveats to be aware of. What happens during the upgrade When Snowflake destination upgrades to 4.0.0 (Direct-Load), the

Disable Final Tables

option is automatically converted to the

Legacy raw tables

option. So if you upgrade without any preparation, your connection will continue writing raw tables only — it won't automatically switch to direct-load final tables. [Snowflake Migration Guide] How to switch to Direct-Load (final tables) Since the two modes (raw-only vs. final tables) are no longer supported in a single connection under 4.0.0, you have two options: Option A: Switch the existing connection to Direct-Load 1. Before upgrading, note that your current connection has

Disable Final Tables

enabled. 2. After upgrading to 4.0.0, the connector will have

Legacy raw tables

enabled automatically. 3. To switch to direct-load, disable the

Legacy raw tables

option in the destination connector config. 4. Be aware this means the connector will now write to final tables only — raw tables will no longer be written. 5. You will likely need to run a refresh/reset on the connection so data is re-synced into the new final table format. Option B: Run both in parallel (if you need both raw and final tables) If you need to keep the raw tables and also get final tables, you must create two separate destination connectors: • One with

Legacy raw tables

enabled (raw tables only) • One with

Legacy raw tables

disabled (final tables via direct-load) Then run two connections in parallel. [Snowflake Migration Guide] [Direct-Load Tables] Additional permission requirement Before upgrading to 4.0.0, make sure your Snowflake user has

ALTER TABLE

permissions, as the new connector requires this for schema evolution. [Snowflake Migration Guide] Summary 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

@kapa.ai Yes I want to switch fully to direct-load (final tables). So, if I upgrade the connector and then disable the raw tables will it convert/keep the history in the raw tables?

I'm sorry, but the knowledge sources do not contain enough specific information about what happens to existing raw table data when you disable

Legacy raw tables

on an already-upgraded 4.0.0 connector. What the knowledge sources do tell us is relevant context: • Under Direct-Load, the connector writes typed data directly to final tables — there is no T+D process that reads from raw tables to populate final tables. [Direct-Load Tables] • The old raw tables are not automatically deleted after an upgrade — they are left untouched. [Upgrading to Destinations V2] Given these two facts, it is unlikely that simply disabling

Legacy raw tables

would automatically convert your existing raw table history into final tables. The direct-load paradigm doesn't use raw tables as a source to build final tables. What I'd recommend The safest approach would be to: 1. Disable

Legacy raw tables

on the destination connector. 2. Run a full refresh/reset on the connection, which will re-sync all data from MySQL directly into the new final tables in the correct Direct-Load format. This ensures your final tables are fully populated, but it does mean re-syncing your historical data from the source rather than converting from the existing raw tables. I'd strongly suggest confirming this with Airbyte's support or community Slack before proceeding, to avoid any unintended data loss. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai What about enabling the final tables in the current connector (<4.0.0) and then upgrading to 4.0.0 snowflake destination connector?

The knowledge sources do not contain enough information to give a confident answer about what happens if you re-enable final tables (disable the "Disable Final Tables" option) on your existing pre-4.0.0 connector before upgrading. What the knowledge sources do tell us is that when upgrading to 4.0.0: • If

Disable Final Tables

is enabled at upgrade time →

Legacy raw tables

is automatically enabled (raw-only mode). [Snowflake Migration Guide] • The upgrade process to 3.0.0 (Destinations V2) involved copying raw table data into the new format — but there's no equivalent description of such a migration path for the 4.0.0 Direct-Load upgrade. [Upgrading to Destinations V2] So while re-enabling final tables before upgrading might result in a cleaner upgrade path, the knowledge sources don't explicitly describe this scenario or guarantee that your raw table history would be carried over into the final tables. I'd strongly recommend reaching out to Airbyte directly via the community Slack or support before attempting this, as the wrong sequence of steps could risk data loss or an inconsistent table state. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.