feat(bigquery): Add support for Bigquery reservations in config #5543
Conversation
This file contains hidden or 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
|
|
scottypate
changed the title
|
This looks good once the build is green |
|
we have been running this in prod for several weeks on our BigQuery deployments and every thing is working as expected. Not super sure how to make CI pass. I have done the pre-commit stuff but still get failures. Any tips of docs for getting me up to speed @izeigerman ? I successfully ran |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Add support for a BigQuery reservation to be specified. This allows users to optionally direct the SQLMesh jobs to a particular BigQuery compute reservation. This is needed for workload management, i.e. you don't want ad-hoc interactive queries blocking data pipelines.