will Snowflake destination connector to ≥4.0.45 br...
# replication-ask-ai
a
will Snowflake destination connector to ≥4.0.45 break exsiting airbyte conections or any issues?
k
Upgrading Snowflake Destination to ≥ 4.0.45 Based on the available knowledge sources, upgrading to 4.0.45 and 4.0.46 are patch-level, non-breaking changes. Here's a summary of what each version fixes and any potential side effects: Version 4.0.45 — Two fixes shipped 1. NULL-safe PK matching restored in dedup MERGE [PR #81530] ◦ A regression introduced in 4.0.44 caused rows with
NULL
values in composite primary key columns to be re-inserted on every sync (unbounded duplication) instead of being deduplicated. ◦ Upgrading to 4.0.45 fixes this. If you were on 4.0.44 with Append+Dedup syncs and composite PKs containing NULLs, you may see deduplication clean up previously duplicated rows. 1. Permission errors now correctly classified as config errors [PR #81420] ◦ Previously, Snowflake
"Insufficient privileges"
errors triggered 5 unnecessary retries and Sentry alerts. ◦ After the fix, these surface immediately as configuration errors — no behavioral change for healthy syncs. Version 4.0.46 — Overwrite sync fix [PR #82134] • Fixes a bug where Full Refresh | Overwrite syncs could incorrectly write directly into an existing table when its
_airbyte_generation_id
was higher than the current sync generation (or mixed). • After the fix, such cases will use a temporary table + final overwrite instead of writing directly. This is the correct behavior and is not a breaking change, but you may notice that some overwrite syncs now go through the temporary table path where they previously didn't. Known Ongoing Issue (not introduced by these versions) There is an existing issue where Full Refresh | Overwrite syncs drop future Snowflake table grants because temporary tables are created in the
airbyte_internal
schema. [GitHub Issue #68681] • This is a behavior change from v4.x in general, not specific to 4.0.45/4.0.46. • Workaround: Apply
FUTURE GRANTS
on the
airbyte_internal
schema in addition to your target schema. The required privileges are
USAGE
,
CREATE STAGE
,
CREATE TABLE
, and
SELECT ON FUTURE TABLES
. Summary No schema, configuration, state format, or stream changes are introduced in either 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