-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
Add priority
parameter to BigQueryHook
#30655
Merged
Merged
Changes from 8 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
b94855b
add priority
ying-w de4b7de
location is also missing
ying-w f778a44
typo
ying-w 54cf25a
fix logic
ying-w 6a5c50e
add test case
ying-w e8c7f72
pass location directly into insert_job
ying-w 5dabb5b
replace deprecated call
ying-w 3787edb
Revert "replace deprecated call"
ying-w 6d4b03a
add deprecation to docstrings
ying-w 1803645
modify test to also check priority
ying-w 0d97b19
typo
ying-w ac6ee40
add location to get_service test
ying-w dc38e96
move location to the right place
ying-w be4f6e7
add priority to examples
ying-w File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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
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.
I'm not sure if this is used in some other way to propagate location to the instance attribute. It isn't the right thing to do but at the same time, I'm worried that an operator was relying on this functionality - especially given the fact that there was a test around this. Can you check if callers of run_query were previously relying on it?
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.
i was just checking what other calls go to
run_query()
and in hooks/bigquery.py theres only 1 other call from deprecatedBigQueryCursor.run_query
which passes in*args, **kwargs
so might rely on itin operators/bigquery.py are 2 calls from within the deprecated
BigQueryExecuteQueryOperator
class just passing through values forexecute()
but doesn't pass inlocation
. Many of these operators setself.location = location
and then pass that toBigQueryHook
So getting rid of the call from
cursor.execute()
should remove calls to run_query() from non-deprecated functions(i checked all references of
run_query
within airflow/providers/google/cloud/)