@kapa.ai I would like to upgrade my Snowflake destination connector from version 3.15 to version 4. Can you point me to relevant documentation, how-tos, to list of caveats and things to pay attention to?

Upgrading Snowflake Destination from v3.x to v4.0 Here's a summary of what you need to know before upgrading: What Changes in v4.0.0 Version 4.0.0 upgrades the connector to the Direct-Load paradigm, replacing the previous Typing and Deduping approach. Key points: [Snowflake Migration Guide] • Improved performance and reduced Snowflake warehouse spend. • New permission required: Your Snowflake user must have

ALTER TABLE

permissions granted before upgrading (needed for schema evolution and table modifications). • CDC deletions can now be enabled as soft-deletes (new option). Migration Paths — Pick Yours Your upgrade path depends on how you interact with Airbyte's tables: [Snowflake Migration Guide] Known Caveats • First sync after upgrading can be very slow if you have a large source. A known issue with v4.0.1 caused many tiny PUT/COPY micro-batches (1 row per COPY). This was fixed in v4.0.3. Make sure you upgrade to the latest patch release (currently 4.0.39+). [GitHub Issue] • A bug causing duplicate records in dedup+truncate mode was fixed in v4.0.39. [GitHub PR] How to Perform the Upgrade 1. Grant

ALTER TABLE

to your Snowflake user before upgrading. 2. Review the changelog at the bottom of the Snowflake destination docs. 3. Navigate to Workspace/Organization settings > Destinations, find the Snowflake connector, and click Change to update to the latest version (self-managed only). 4. For each connection using this destination, select the connector instance and click Upgrade. 5. After upgrading, refresh the source schema (Connections > Schema tab > Refresh source schema) and clear data for affected streams if needed. [Connector Upgrade Guide] > Tip: If you cannot upgrade immediately, you can pin your connector to v3.x via Workspace/Organization settings > Destinations > edit the connector > set Default Version. 👍 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 Do you mean it is possible to activate the new version just on some connections? This would be very useful for testing

Yes, this is possible! When upgrading connectors, each instance must be updated separately — updating one connection does not affect the others. [Managing Connector Updates] For a safe testing approach, the documentation specifically recommends a dual-writing strategy: 1. Update the default destination version in your workspace to v4.0.0. 2. Create a new destination pointing to the same Snowflake database, but with a different

Default Schema

to avoid collisions with your existing data. 3. Create a new connection using your existing source and this new destination, matching the settings of your pre-existing connection. 4. Enable and test this new connection while your original connection continues running on the old version undisturbed. [Upgrading with Dual-Writing] This way you can validate the v4.0.0 behavior on real data before committing to upgrading your production connections. > Note: If any of your streams use incremental sync mode, there are additional steps to follow for those streams specifically before enabling the new connection. The documentation covers this in the dual-writing upgrade guide. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.