-
Notifications
You must be signed in to change notification settings - Fork 58
refactor: Unify bigquery execution paths #2007
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
Merged
+375
−359
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
e65e8a6
refactor: Unify bigquery execution paths
TrevorBergeron 1c20901
fix usage of options._allow_large_results
TrevorBergeron ced3618
fix tokyo tests, improve prepare_plan helper
TrevorBergeron 31853d4
Merge remote-tracking branch 'github/main' into session_simplify
TrevorBergeron 03249a1
fix cluster col comparison
TrevorBergeron 4d51fd2
Merge remote-tracking branch 'github/main' into session_simplify
TrevorBergeron f8da6f8
fix incompatible clustering check
TrevorBergeron 62d4314
Merge branch 'main' into session_simplify
TrevorBergeron File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
This threshold hasn't changed in a decade+, but I'm still wary of including it in the name. Perhaps
requires_explicit_destination
would better reflect the backend API?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.
Chatted offline. This is intended to be somewhat backend-independent rather than prescriptive about constructing a table. Even if the threshold changes, it would only be to go up (to avoid breaking changes), so this naming should be OK, even if slightly inaccurate in that theoretical future.