Skip to content

Commit

Permalink
doc: in query retry design, note that location can be required (#1595)
Browse files Browse the repository at this point in the history
In response to internal issue 285136859.

Co-authored-by: Anthonios Partheniou <[email protected]>
  • Loading branch information
tswast and parthea committed Jul 6, 2023
1 parent 130450a commit 6682055
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/design/query-retries.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ value, the client library uses the jobs.insert REST API to start a query job.
Before it issues this request, it sets a job ID. This job ID remains constant
across API retries.

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.
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.


#### Retrying the jobs.query API via the retry parameter
Expand Down

0 comments on commit 6682055

Please sign in to comment.