-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v2.0.0-alpha.10] BigQuery doesn't connect to regions that are not US #6937
Comments
@gusfune Thanks for reporting this. We are looking into this and we will get back to you as soon as possible. |
Hi Gus, (I'll assume that this cascade of errors by Google Cloud is unrelated.) This is not an expected behavior -- we don't put any region information in the backend's communication with the BigQuery APIs. Can you share the error message that you're seeing? One possible explanation is that the service account is restricted to a region, but I'd have to see more information. |
Hi @chrisdone I will be glad to help.
Here is also the error captured from the logs:
Extra info:
Let me know if you need more info. |
The name is odd: This feels like a JavaScript bug that has leaked into the system. Can you confirm whether your dataset is really named |
Huh. Actually the dataset is
It responds:
Then the query request goes:
|
@beerose Does the console make any |
@gusfune Are you certain that the query that you have shared is what fails? What code does the server return? |
@0x777 I am certain that the query that is failing is this one (Sending below in more details). To replicate the issue this is what happens:
I did some extra snooping around and on Here is the query that returns 400:
RESPONSE:
Here is also a full log output from starting the instance to the moment I get the error query:
|
…from a non-US region Fixes [issue](#6937) ### Description The problem lies with the `schemaListSql` for Big Query. Without a region qualifier prefixed, the SQL result contains datasets only US regions, as described in the [docs](https://cloud.google.com/bigquery/docs/information-schema-datasets). ``` If you do not specify a regional qualifier, metadata is retrieved from the us multi-region. ``` The alternative way is to get a list of all available publicly available regions (which is `us` and `europe` atm), for example for europe - ``` SELECT * FROM region-europe.INFORMATION_SCHEMA.SCHEMATA; ``` and then perform `UNION ALL` of the results. This is approached is ditched in favour of the reason that Big Query is read-only on Hasura and new datasets cannot be added from the console (other than by modifying the metadata), we can return the datasets available in the Big Query source's metadata as the possible values of datasets needed by the console to render the data nav tree, thereby avoiding an extra API call in the process. GitOrigin-RevId: 8117d56
Fixed in 3acfd35 |
@gusfune Can you try this build which has the fix: |
It did the connection @0x777 , but now the error is:
In the console I get:
Maybe it's a different issue. Then I am not sure. Might be related to the fact it's a pre-existing database. |
@gusfune I think it'll be easier for us to debug this if we can reproduce this on our end. I tried creating a new dataset, but |
I will be glad to help out @0x777, do you want to hop in a google meets anytime soon? https://calendly.com/gusfune |
This was fixed, confirmed with @0x777 on slack |
BigQuery only connects to datasets hosted in the
US
region.I could not connect as my datasets are in
europe-west3
. There are other regions as well that needs.The text was updated successfully, but these errors were encountered: