It may be a bit of a silly question, but how can one propagate location setting when creating job against BigQuery table?
Something like your pagination.rs example, but with location set?
Looking through the source code/docs it is not really obvious where it needs to be set - I'd assume it to be part of JobConfigurationQuery but doesn't look like that struct has a location field
I tried to use ConnectionProperty (which is field of JobConfigurationQuery) but doesn't look like a correct option
And as far as I can see hereJobConfigurationQuery is the only thing which is can be passed down to the actual call to create the job
Would definitely appreciate some help on this one :)
UPD:
Found this LoC - so one can specify location of the job, however it seems not be exposed when calling client.job().query_all - so feels like a small bug (unless I am missing something else here)
Hello there,
It may be a bit of a silly question, but how can one propagate
locationsetting when creating job against BigQuery table? Something like yourpagination.rsexample, but with location set?Looking through the source code/docs it is not really obvious where it needs to be set - I'd assume it to be part of
JobConfigurationQuerybut doesn't look like that struct has a location fieldI tried to use
ConnectionProperty(which is field ofJobConfigurationQuery) but doesn't look like a correct option And as far as I can see hereJobConfigurationQueryis the only thing which is can be passed down to the actual call to create the jobWould definitely appreciate some help on this one :)
UPD: Found this LoC - so one can specify
locationof the job, however it seems not be exposed when callingclient.job().query_all- so feels like a small bug (unless I am missing something else here)