Database Reference
In-Depth Information
"message": "Not Found: Dataset
bigquery-e2e:nonexistent"
}
When you run a query against a nonexistent dataset, which creates a job,
you get a nearly identical error in the
job.errorResult
field:
"errorResult": {
"reason": "notFound",
"message": "Not Found: Dataset
bigquery-e2e:nonexistent"
}
Error Reporting for Jobs.query() and Jobs.getQueryResults()
The lines between a job error and an HTTP error get murkier when you
consider the
Jobs.query()
and
Jobs.getQueryResults()
APIs.
These APIs wait for a query to complete and return the results. The
Jobs.query()
API is designed to be callable in a synchronous
fashion—having to distinguish between errors in the request and network
errors, and errors in the job would be too onerous. For this reason, the
Jobs.query()
and
Jobs.getQueryResults()
methods that hit a fatal
error (that is, the Query job has a
status.errorResult
) return those
errors as HTTP errors. For example, the same query that previously
generated the
notFound errorResult
would return the following HTTP
response code if executed via the
jobs.query()
API:
{
"error": {
"errors": [
{
"domain": "global",
"reason": "notFound",
"message": "Not Found: Dataset
bigquery-e2e:nonexistent"
}
],
"code": 404,
"message": "Not Found: Dataset
