-
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
Fix issues around new get_catalog_by_relations macro #8856
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #8856 +/- ##
==========================================
+ Coverage 86.31% 86.44% +0.13%
==========================================
Files 177 177
Lines 26385 26405 +20
==========================================
+ Hits 22775 22827 +52
+ Misses 3610 3578 -32
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
I think we might have introduced a pre-regression with this PR. See the details here: dbt-labs/dbt-snowflake#816. |
* Fix issues around new get_catalog_by_relations macro * Add changelog entry * Fix unit test. * Additional unit testing
* Fix issues around new get_catalog_by_relations macro (#8856) * Fix issues around new get_catalog_by_relations macro * Add changelog entry * Fix unit test. * Additional unit testing * Fix cased comparison in catalog-retrieval function (#8940) * Fix cased comparison in catalog-retrieval function. * Fix cased comparison in catalog-retrieval function.
resolves #8846
Problem
An optional parameter was added to BaseAdapter.get_catalog() in 1.7.0rc1, which was unfortunately overridden by databricks, and may also be overridden in other adapter implementations.
Solution
This changeset reverts the function to its original signature, and adds a new function called BaseAdapter.get_filtered_catalog(). It also reworks the
docs generate
code which had relied previously relied on the new parameter.Significantly, the filtering is now performed against a set of BaseRelation objects passed to the adapter, instead of a set of nodes. This reduces the number of concepts that leak into the adapter, which should not need to "know" about the dag or nodes.
Checklist