Closed christopherekfeldt closed 1 year ago
Thanks for reaching out @christopherekfeldt !
It looks like materialized
is misspelled as materalized
within your YAML. Could you try updating the spelling and see if it works?
Well isn't that embarrassing.. Thanks, @dbeatty10 it works perfectly fine now.
No problem @christopherekfeldt. Glad it's working the way you want now 🙌
Is this a new bug in dbt-core?
Current Behavior
We are trying to set all configurations through a models yml file and keep the models SQL file clean. We have been noticing a disturbing issue with setting materializations through the models yml file. Where it doesn't attach.
For example this is a models yml file:
This will still try to create it as a view, even if I try recreating it with --full-refresh. The SQL-file only contains SQL-code and jinja, with no configurations. We have not set a default materialization in our dbt_project.yml.
When i add the config to my SQL at the top like:
{{ config(materialized='table') }}
Then the model is recreated as I want. But we want to keep all configurations in the yml file alone.
Expected Behavior
That the model is created as the materialization i set in the models yml file.
Steps To Reproduce
Relevant log output
Environment
Which database adapter are you using with dbt?
bigquery
Additional Context
No response