Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
"[notFound]" error but query was successful in logs #274
Following the documentation in the readme for the sample data worked for me no problems. However when I switched to my own dataset (using the project that I used for billing on sample data) I am never able to return results and am always faced with the error:
Listing tables and their contents works no problem:
dplyr test - this fails with error mentioned before:
Interestingly though, when I check the logs in the BigQuery web UI I can see the successful queries that R isn't returning.
I've tried authenticating via OAuth and with a JSON token that I've created. Making sure that the user has full access to BigQuery API's.
Also have tried all methods for submiting the query (
I begun digging around the source code and trying to use
Note: Data is stored and processed in australia-southeast1.
Is this expected behaviour and I've glossed over something simple?
I'm having exactly the same issue. Public datasets are fine, and I can use
all successfully against my private dataset - but can't execute a query - always get the same error as above, and as above, I can see the query executed successfully, and the name of hte job appears to match the result set
Even more of a coincidence though is that we also have our data stored against australia-southeast1
Going to see if a colleague can load some data to another location to see if that changes things.
After we execute a query using (for example)
I don't know R (I am looking at BigRQuery to help @extrobe, so I don't fee confident enough in building a PR to fix this.
As far as I can tell, the
I modified part of
Which is good to know as there then just needs to be a way to feed through the location parameter.
So it might be a more involved fix to add support for regions unless there is a region specified upfront or determined at the time of the GET request?
@hadley I'm happy to work on the fix if you can lend some guidance.
The fix complexity is compounded because it undoes some of the efficiency of bq_refs.R, with the job being the only thing that requires a region.
I'm sorry I cannot help more with the code, but with my 90 minutes of experience of R I'm sure I'm going to break things more than I fix them!
This now just works for a simple example:
asia <- bq_test_dataset(location = "asia-east1") tb <- bq_table(asia, "mtcars2") bq_table_upload(tb, mtcars) bq_table_download(tb)
But I'd appreciate it if someone would try the development version for a real problem, and provide a reprex if there are still problems.
@hadley ran into this issue again, seems like some functions still exhibit the bug, specifically I get the issue with
The above works fine, but the below fails with
I got around this by using