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

BigQuery: Add dryrun option to magic. #8143

Closed
jpallas opened this issue May 25, 2019 · 4 comments
Closed

BigQuery: Add dryrun option to magic. #8143

jpallas opened this issue May 25, 2019 · 4 comments
Assignees
Labels
api: bigquery Issues related to the BigQuery API. good first issue This issue is a good place to started contributing to this repository. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@jpallas
Copy link

jpallas commented May 25, 2019

The BQ API supports the dry_run option, but the ipython magic does not. It would be great if there were a parameter which, when set, would return the (sometimes vital) information about bytes to be read instead of running the query. This would help put the Jupyter environment on a par with the BQ console.

@tseaver tseaver added api: bigquery Issues related to the BigQuery API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels May 25, 2019
@tseaver tseaver changed the title Add dryrun option to BigQuery magic BigQuery: Add dryrun option to magic. May 25, 2019
@tswast
Copy link
Contributor

tswast commented Jun 3, 2019

FYI: there's an open PR at #8179 which will add context.default_query_job_config, so that this will be possible to set globally.

I agree that a parameter would make sense for this option. See #8179 for implementation and testing patterns.

@tswast tswast added the good first issue This issue is a good place to started contributing to this repository. label Jun 3, 2019
@tswast
Copy link
Contributor

tswast commented Jun 4, 2019

Likely for --dryrun queries we'll want to print out something other than an empty DataFrame the estimated bytes processed and maybe additional stats if relevant.

Maybe return a QueryJob instead of a DataFrame for inspection.

@jpallas
Copy link
Author

jpallas commented Jun 4, 2019

Yes, my thinking was to provide (at least) the same cost feedback that the BQ console interface does.

@tswast
Copy link
Contributor

tswast commented Aug 23, 2019

Closed by #9067.

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. good first issue This issue is a good place to started contributing to this repository. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

3 participants