Repository navigation
BigQuery: Add dryrun option to magic. #8143
Description
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.
Activity
[-]Add dryrun option to BigQuery magic[/-][+]BigQuery: Add dryrun option to magic.[/+]tswast commentedon 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 commentedon Jun 4, 2019
Likely for
--dryrunqueries 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
QueryJobinstead of aDataFramefor inspection.jpallas commentedon Jun 4, 2019
Yes, my thinking was to provide (at least) the same cost feedback that the BQ console interface does.
tswast commentedon Aug 23, 2019
Closed by #9067.