-
Notifications
You must be signed in to change notification settings - Fork 157
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
Using information schema #238
Using information schema #238
Conversation
currently running into the same issue and found this PR, looks like there are conflicts in this branch. |
@@ -473,8 +473,17 @@ def test_replace(self): | |||
relation = BigQueryRelation.from_dict(kwargs) | |||
info_schema = relation.information_schema() | |||
|
|||
tables_schema = info_schema.replace(information_schema_view='__TABLES__') | |||
assert tables_schema.information_schema_view == '__TABLES__' | |||
tables_schema = info_schema.replace(information_schema_view='INFORMATION_SCHEMA.TABLES') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TABLE_STORAGE
is also needed for multi-region BigQuery setups as illustrated in this macro workaround this PR is solving for natively: https://github.com/GeneralMills/gmi_common_dbt_utils/blob/main/macros/bq_catalog.sql#L51
@hassan-mention-me Any updates on this? |
This is something General Mills is also interested in seeing |
Closing this in favor of getting #364 over the line |
resolves #113 #113
Using
information_schema
instead of TABLES to fetch catalog data, which limits access level needed to generate DBT docs.Checklist
CHANGELOG.md
and added information about my change to the "dbt-bigquery next" section.