Skip to content
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

feat(bigquery): add support for custom QueryJobConfig in BigQuery.cursor.execute method #9278

Merged

Conversation

TobKed
Copy link
Contributor

@TobKed TobKed commented Sep 24, 2019

My change allows to support use_legacy_sql.

@TobKed TobKed requested a review from a team September 24, 2019 12:18
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Sep 24, 2019
@TobKed TobKed force-pushed the support-custom-config-for-cursor-execute branch 2 times, most recently from 942cfff to dd170ac Compare September 24, 2019 12:42
@TobKed TobKed force-pushed the support-custom-config-for-cursor-execute branch from dd170ac to 7d23584 Compare September 24, 2019 12:42
@plamut plamut added the api: bigquery Issues related to the BigQuery API. label Sep 24, 2019
@plamut plamut changed the title Add support for custom QueryJobConfig in BigQuery.cursor.execute method feat(bigquery): add support for custom QueryJobConfig in BigQuery.cursor.execute method Sep 24, 2019
Copy link
Contributor

@plamut plamut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this!

Before merging, though, we would still need to add the new parameter description to the method's docstring, and cover the change in the tests. We would be happy to provide any assistance, should that be necessary.

@TobKed
Copy link
Contributor Author

TobKed commented Sep 24, 2019

Thanks for feedback @plamut . I've applied changes suggested by you however still waiting for Kokoro check.

@plamut plamut added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 24, 2019
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 24, 2019
@plamut plamut added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 25, 2019
@yoshi-kokoro yoshi-kokoro removed kokoro:force-run Add this label to force Kokoro to re-run the tests. labels Sep 25, 2019
@TobKed
Copy link
Contributor Author

TobKed commented Sep 25, 2019

Kokoro - Recommender check has failed however logs are empty. @plamut do you know maybe why it failed? I have no clue what is the reason.

@plamut
Copy link
Contributor

plamut commented Sep 25, 2019

@TobKed Seems like flakiness, saw the same on a few other PRs as well. I will try restarting the jobs.

Update: Actually, it seems to be a real issue in the Recommender library, not just flakiness. It currently happens on all PRs, and it's not related to the changes made here.

@plamut plamut added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 25, 2019
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Sep 25, 2019
Copy link
Contributor

@plamut plamut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, a custom job config indeed changes the SQL mode for the job on the backend.

@TobKed
Copy link
Contributor Author

TobKed commented Sep 25, 2019

@plamut thanks for feedback! Good luck with fixing Kokoro :)

Copy link
Contributor

@tswast tswast left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I'm a bit concerned about deviating from the DB-API spec for execute(), but I see we already deviate due to job_id.

@plamut plamut merged commit 7c9c0cb into googleapis:master Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the BigQuery API. cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants