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
ATM it's only possible to configure an explicit warehouse to explicit models.
In a scenario with many small models + 2-3 big models (data volume/ runtime) you would probably go to environmental config like this:
environment: PRODUCTION
warehouse: SMALL
virtuell warehouse ( for big models ): XL
Problem: It's not possible to influence the runtime of tests on your big model without changing the standard warehouse, which would potentially lead to a massive cost increase.
Describe alternatives you've considered
It would be possible to write tests as models and to test against these.
Problem: unnecessary models in repo and lineage
Additional context
Please include any other relevant context here.
Who will this benefit?
Cost sensitive customers.
Are you interested in contributing this feature?
Let us know if you want to write some code, and how we can help.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Snowflake: Configuration of virtuell warehouses for tests
[CT-1039] Snowflake: Configuration of virtuell warehouses for tests
Aug 15, 2022
Describe the feature
Extend the configuration of virtuell warehouses to tests.
https://docs.getdbt.com/reference/resource-configs/snowflake-configs#configuring-virtual-warehouses
ATM it's only possible to configure an explicit warehouse to explicit models.
In a scenario with many small models + 2-3 big models (data volume/ runtime) you would probably go to environmental config like this:
environment: PRODUCTION
warehouse: SMALL
Problem: It's not possible to influence the runtime of tests on your big model without changing the standard warehouse, which would potentially lead to a massive cost increase.
Describe alternatives you've considered
It would be possible to write tests as models and to test against these.
Problem: unnecessary models in repo and lineage
Additional context
Please include any other relevant context here.
Who will this benefit?
Cost sensitive customers.
Are you interested in contributing this feature?
Let us know if you want to write some code, and how we can help.
The text was updated successfully, but these errors were encountered: