-
Notifications
You must be signed in to change notification settings - Fork 5
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
DBT 0.21.0 requires new configuration to override global DBT macros #1
Comments
@mroy-seedbox did you get this to work? I'm struggling with this |
Yup, all you need is something like this in your name: my_project
# Allow my macros to override global DBT macros
dispatch:
- macro_namespace: dbt
search_order: ['my_project', 'dbt'] |
This is strange, I did this but it gives me |
That is weird indeed! But I've never tested it with Postgres (only with Snowflake)... maybe there's something missing to make it work? 🤔 |
Try with something like this: # Allow my macros & DDO macros to override global DBT macros
dispatch:
- macro_namespace: dbt
search_order: ['my_project', 'dbt_packages/DDO/macros', 'dbt'] |
Same issue :(
|
Try with
|
Same result with this config. It is a good point that I was using the old name, but unfortunately it didn't change the output.
|
Have you tried creating a copy of the materialization in your own project? If that doesn't work, then it must be something specific to do with the DBT Postgres implementation. 😕 |
@AdrianCio: did it work? 😅 |
Apologies, I was off for a week. Indeed I ended up copying the materialization in my project which works fine. |
See https://docs.getdbt.com/reference/dbt-jinja-functions/dispatch#overriding-global-macros
The text was updated successfully, but these errors were encountered: