Add dry run support #30
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
|
💚 💙 💜 💛 ❤️ |
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.
Context
It is good practice for BigQuery queries to be run in dry run mode before actually running the query when on-demand pricing model is used. That way, the total amount of bytes that a query would process can be known beforehand, enabling users to make fine adjustments to it in case the resulting costs are too high.
Currently, req_bigquery offers no support to run BigQuery queries in dry run mode, nor does it return the associated total bytes that the query processed.
Proposed solution
dry_runoption to run queries in dry run mode;total_bytes_processedtoReqBigQuery.Resultto present the result;