-
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
catalog.json
file does not contain sources with dbt-postgres 1.7.8
#9678
Comments
@bdtoole #9493 is one possibility. It touched on the same code as this PR, and it fixed #9161 By any chance, are you using a selector similar to this? dbt docs generate --select something_other_than_sources If so, what happens if you add dbt docs generate --select something_other_than_sources resource_type:source |
Hey @dbeatty10 - great thought! I'm not using select criteria like that, but I did override the default selector while I build out our new dbt infrastructure:
When I change the default back to false, sources end up in the catalog as expected. When I keep default as true, sources do not end up in the catalog. |
Could you try adding this to your - method: resource_type
value: source # Include sources I tried out the following, and
selectors:
- name: default_prod
description: The default production selector
default: true # Todo for future: Change to include target-aware logic
definition:
union:
- method: fqn # Fully qualified name
value: '*' # Everything
- method: resource_type
value: source # Include sources
- exclude:
- method: fqn # Fully qualified name
value: marts
- method: fqn
value: staging |
I added that and it worked! So why is this necessary now in 1.7.x? Is there a bug that's preventing sources from getting pulled back by the fqn + * combination or is this an undocumented feature? 😆 |
dbt-postgres 1.7.8
catalog.json
file does not contain sources with dbt-postgres 1.7.8
Glad that worked for you! 🎉 This is necessary now in 1.7.x because of #9161 which was fixed by #9493. I'm guessing that neither sources nor analyses were ever getting selected by the fqn + * combination, so I opened these issues accordingly:
Thanks again for reporting this. I'm going to close this issue in favor of those two. |
Originally posted by @bdtoole in #9119 (comment)
The text was updated successfully, but these errors were encountered: