BigQuery: Add default location to Client #5148
Assignees
Labels
api: bigquery
Issues related to the BigQuery API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
tswast
added
type: feature request
|
I imagine the number of defaults we'd want to set will grow (encryption configuration, maximum bytes billed, etc.) but |
This was referenced Apr 7, 2018
tseaver
added a commit
that referenced
this issue
Jul 25, 2018
* Add read-only 'Client.location' property. Settable via new 'location' argument to ctor. * Use 'Client.location' as default for 'Client._get_query_results'. * Use 'Client.location' as default for 'Client.get_job'. * Use 'Client.location' as default for 'Client.cancel_job'. * Use 'Client.location' as default for 'Client.load_table_from_uri'. * Use 'Client.location' as default for 'Client.load_table_from_file'. * Use 'Client.location' as default for 'Client.load_table_from_dataframe'. * Use 'Client.location' as default for 'Client.copy_table'. * Use 'Client.location' as default for 'Client.extract_table'. * Use 'Client.location' as default for 'Client.query'. * Use 'Client.location' as default default for 'create_dataset'. Closes #5148.
|
🎉 Thanks Tres! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is potentially quite cumbersome to pass in a
locationparameter to nearly every API request method. It would be nice to set a defaultlocationwhen you create a client to be used when creating datasets or jobs.The text was updated successfully, but these errors were encountered: