You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2022. It is now read-only.
Is your feature request related to a problem? Please describe.
When running queries on metatables that are available in multiple locations (INFORMATION_SCHEMA), there should be an option to choose override processing location as in our case, running the same query in 2 locations returns different values.
Describe the solution you'd like
A selector in the UI that allows specifying processing location for each query.
Describe alternatives you've considered
N/A
Teachability, Documentation, Adoption, Migration Strategy
This could be set to default (US), so existing users should not be affected.
Let me know if you need more info.
Thanks,
Nauris
The text was updated successfully, but these errors were encountered:
Just to add to the previous comment, in our case BigQuery Flat Rate is tied to a specific region (EU), so running queries across global meta tables (US) actually cost us money. Hope this helps!
Hi @avivl it would be good to be able to set the default location on the data source. Since we store everything in the EU I now have to go through hundreds of graphs to change the location.
I'm also missing the ability to set the location for variable queries.
Feature Request
Is your feature request related to a problem? Please describe.
When running queries on metatables that are available in multiple locations (
INFORMATION_SCHEMA
), there should be an option to choose override processing location as in our case, running the same query in 2 locations returns different values.Describe the solution you'd like
A selector in the UI that allows specifying processing location for each query.
Describe alternatives you've considered
N/A
Teachability, Documentation, Adoption, Migration Strategy
This could be set to default (
US
), so existing users should not be affected.Let me know if you need more info.
Thanks,
Nauris
The text was updated successfully, but these errors were encountered: