-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
In projects named warehouse
, Snowflake warehouse config gets confused
#1899
Comments
Oh no, this is terrible. I think we need to add |
I just tested a project that is not named Is there a way to more tightly scope the |
@beckjake let's rename Let's also revisit this question in a future release to figure out how to make dbt's config structure unambiguous. This will all break if people have projects or paths named |
…wflake-warehouse rename "warehouse" config key to "snowflake_warehouse" (#1899)
Describe the bug
If a dbt project is named
warehouse
, almost all Snowflake models running in the 0.15.0 beta release experience the following error:This is caused by the changes in #1788, which allow per-model Snowflake warehouse specification using a
warehouse
config argument. If a dbt project is also namedwarehouse
, confusion ensues.In an example
dbt_project.yml
:For all models that do not have a
warehouse
config argument specified, Instead of skipping theuse warehouse
statement altogether, dbt is runningI believe the relevant line is here of
pre_model_hook
, wherebyconfig.get('warehouse', default_warehouse)
returns... not thewarehouse
we're looking for.Steps To Reproduce
Name your dbt project
warehouse
, and run any model on Snowflake without awarehouse
config.Expected behavior
A model with no
warehouse
config should always behave exactly the same as a model configuredSystem information
Which database are you using dbt with?
The output of
dbt --version
:Additional context
The easiest solution here is to rename the dbt project to something other than
warehouse
. For that reason, I would understand if this is a #wontfixThe text was updated successfully, but these errors were encountered: