Skip to content
This repository has been archived by the owner on Nov 11, 2022. It is now read-only.

BigQueryTableRowIterator should allow non-default location for temporary data set #86

Closed
nevillelyh opened this issue Dec 3, 2015 · 4 comments
Assignees
Labels

Comments

@nevillelyh
Copy link
Contributor

It seems that a query request may fail if the destination dataset is not in the same region as original table being queried.
Newly created datasets are in "US" by default and will fail if table being queried is in "EU".

@dhalperi dhalperi added the bug label Dec 10, 2015
@dhalperi dhalperi self-assigned this Dec 10, 2015
@dhalperi
Copy link
Contributor

Hi Neville,

Thanks for reporting this. We're working on a fix.

@dhalperi
Copy link
Contributor

dhalperi commented Mar 7, 2016

BigQuery now will tell you what location a query will run in when you dry_run it. We now use this information to set the location for the temporary dataset -- so this issue should be fixed without any API changes.

Thanks!
Dan

@dhalperi dhalperi closed this as completed Mar 7, 2016
@nevillelyh
Copy link
Contributor Author

Just curious how do you get this information with the BQ Java client?
I'm using com.google.apis:google-api-services-bigquery:v2-rev275-1.21.0 and don't see a location field in the dry run job response.

@dhalperi
Copy link
Contributor

@nevillelyh - right now I believe the field is only populated when you dry run an insert job.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants