Snowflake destination: table-level grants lost after each sync when using Incremental Append+Deduped mode #75278
lukewatters-airbyte
started this conversation in
Connector Ideas and Features
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
When using the Snowflake destination connector with Incremental Append+Deduped sync mode, table-level grants are lost after every sync. This happens because the connector uses ALTER TABLE ... SWAP WITH for deduplication, but does not include COPY GRANTS in the operation. As a result, any downstream users or roles that depend on table-level permissions lose access after each sync — requiring manual re-application of grants to restore access. This disrupts automated data workflows and causes unexpected access issues for reporting users and downstream consumers.
Proposed Solution
The connector should include COPY GRANTS when performing ALTER TABLE SWAP operations during Incremental Append+Deduped syncs. Alternatively, a configuration toggle could be added to enable this behaviour for users who rely on table-level grants. As a near-term measure, the docs should clearly describe this limitation and suggest workarounds such as schema-level grants or Snowflake FUTURE GRANTS.
Who benefits
Any team using the Snowflake destination connector with Incremental Append+Deduped sync mode where downstream users, BI tools, or automated pipelines depend on table-level permissions in Snowflake.
Additional context
Workarounds include using schema-level grants or configuring Snowflake FUTURE GRANTS to automatically apply permissions to new/swapped tables — but these require changes outside of Airbyte and don't fix the underlying connector behaviour.
Beta Was this translation helpful? Give feedback.
All reactions