Database Reference
In-Depth Information
the message so that you can find out what it
is that has been blacklisted.
403
rateLimitExceeded
You're sending BigQuery requests too
quickly; try slowing down.
403
quotaExceeded
You've exceeded a long-term (most likely
daily) quota limit.
404
notFound
You tried to access a resource that doesn't
exist.
409
duplicate
You tried to create a resource that already
exists.
500
internalError
Your response triggered an internal
BigQuery error. This is always a BigQuery
bug.
503
backendError
There was an error connecting to BigQuery,
or BigQuery experienced an error
contacting another required service. If you
retry, this error will likely go away.
Job Errors and Responses
Most BigQuery errors are reported as an HTTP error of the type described
in the previous section. However, when you run a BigQuery job, it gets run
asynchronously. Errors that are encountered on the job may not happen
in the context of an HTTP request. To report errors, jobs use the
status.errorResult
and
status.errors
fields. These are described
in more detail in the more detail in the “Jobs” section in this chapter.
Job errors are reported using the same data structure as the HTTP response
errors. The only difference is that they do not have an HTTP response code
because they aren't HTTP errors. But they look virtually identical to the
HTTP responses.
For example, when you try to read a dataset that doesn't exist, you get the
following error in the
errors
field of the response:
{
"domain": "global",
"reason": "notFound",
