-
Notifications
You must be signed in to change notification settings - Fork 999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add refresh_mode
and initialize
for snowflake dynamic table configuration
#5701
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This is failing, but I don't have Vercel access so I can't see why. I'm assuming it's either that I am throwing version blocks in the middle of yaml blocks and tables or that I'm adding a first version of 1.9. |
These are small configuration changes that are specific to a single adapter. Is it worth noting in the migration guide? I notice that's an item in the checklist. |
Adding spaces between brackets and content
@@ -400,6 +421,12 @@ models: | |||
[on_configuration_change](/reference/resource-configs/on_configuration_change): apply | continue | fail | |||
[target_lag](#target-lag): downstream | <time-delta> | |||
[snowflake_warehouse](#configuring-virtual-warehouses): <warehouse-name> | |||
<VersionBlock firstVersion="1.9"> | |||
|
|||
[refresh_mode](#refresh-mode): AUTO | FULL | INCREMENTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the version blocks don't work inside of the code blocks. Will change this to a text warning rather than version blocking the whole tab setup
What are you changing in this pull request and why?
We added two new configuration options for the dynamic table materialization in
dbt-snowflake
:refresh_mode
andinitialization
. These options are specific todbt-snowflake
.They are available in dbt Cloud and will be introduced in 1.9 in dbt Core.
Checklist