You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we’re trying to figure out the best way to make sure the change_tracking setting persists with our DBT model. Do you (or anyone from Snowflake in this thread) have any documentation regarding how to set change_tracking in a DBT model’s config?
[When TRUE it] adds a pair of hidden columns to the source table and begins storing change tracking metadata in the columns. These columns consume a small amount of storage.
The change tracking metadata can be queried using the CHANGES clause for SELECT statements, or by creating and querying one or more streams on the table.
Additional Info
Describe alternatives you've considered
user makes a custom materialization to do so. not ideal
Snowflake makes CHANGE_TRACKING=TRUE the new default so we need not make it explicit
Who will this benefit?
Any user who relies on change_tracking, Dynamic Tables (dependencies of Dynamic Tables must have change_tracking=true), and streaming scenarios in Snowflake
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is this your first time submitting a feature request?
Describe the feature
Context
User request (internal Slack thread):
This is not currently possible
Reference
Snowflake SQL Reference:
CREATE TABLE
Additional Info
Describe alternatives you've considered
CHANGE_TRACKING=TRUE
the new default so we need not make it explicitWho will this benefit?
Any user who relies on
change_tracking
, Dynamic Tables (dependencies of Dynamic Tables must havechange_tracking=true
), and streaming scenarios in SnowflakeAre you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: