Skip to content
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 empty when custom schema names used #2653

Closed
Plamen8780 opened this issue Jul 28, 2020 · 2 comments
Closed

catalog.json file empty when custom schema names used #2653

Plamen8780 opened this issue Jul 28, 2020 · 2 comments
Labels
bug Something isn't working redshift
Milestone

Comments

@Plamen8780
Copy link

https://github.com/fishtown-analytics/dbt/blob/3ec911b62c736e7b5ae26e624b9a981dc3fb177f/plugins/redshift/dbt/include/redshift/macros/catalog.sql#L46
The line above does not take into account custom schema names and it always refers to the default schema name.
This results in an empty catalog.json file whenever the target uses custom schema names.
This issue appeared first appeared in v.0.17.0

@jtcohen6 jtcohen6 added this to the 0.17.2 milestone Jul 28, 2020
@jtcohen6 jtcohen6 added bug Something isn't working redshift labels Jul 28, 2020
@jtcohen6
Copy link
Contributor

Thanks for raising this! The straightforward solution here should be to include all schemas in the filter, along the lines of the approach we take in postgres:
https://github.com/fishtown-analytics/dbt/blob/5b40cc4a01d1ce3ef06e60d70bc7d293cd193855/plugins/postgres/dbt/include/postgres/macros/catalog.sql#L33-L37

We'll try to get this in for 0.17.2.

@jtcohen6
Copy link
Contributor

Closed by #2654

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working redshift
Projects
None yet
Development

No branches or pull requests

2 participants