Skip to content
This repository was archived by the owner on Mar 6, 2026. It is now read-only.

Commit 6682055

Browse files
tswastparthea
andauthored
doc: in query retry design, note that location can be required (#1595)
In response to internal issue 285136859. Co-authored-by: Anthonios Partheniou <partheniou@google.com>
1 parent 130450a commit 6682055

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/design/query-retries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ value, the client library uses the jobs.insert REST API to start a query job.
7373
Before it issues this request, it sets a job ID. This job ID remains constant
7474
across API retries.
7575

76-
If the job ID was randomly generated, and the jobs.insert request and all retries fail, the client library sends a request to the jobs.get API. This covers the case when a query request succeeded, but there was a transient issue that prevented the client from receiving a successful response.
76+
If the job ID was randomly generated, and the jobs.insert request and all retries fail, the client library sends a request to the jobs.get API. This covers the case when a query request succeeded, but there was a transient issue that prevented the client from receiving a successful response. Note: `jobs.get` requires the location of the query. It will fail with 404 if the location is not specified and the job is not in the US multi-region.
7777

7878

7979
#### Retrying the jobs.query API via the retry parameter

0 commit comments

Comments
 (0)