Bigquery sqlalchemy metastore #1352
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aidenprice
pushed a commit
to arrowtail-precision/querybook
that referenced
this pull request
Jan 3, 2024
* [bigquery] bump bigquery engine dependencies * [bigquery] Allow use of Application defaults credentials if no credentials specified * [metastore] Split table name on '.' when using sqlalchemy-bigquery metasore
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Merge request allow the use of sqlalchemy-bigquery as a metastore for bigquery engine.
Also bump bigquery requirements files and add sqlalchemy-bigquery dependency.
Allow use of empty google credentials for bigquery engine : In case of running in GKE cluster, we can use in cluster service account with workload identity to authenticate to google.
It Fix : #517