Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add missing docs for timeout exceptions (#10554) 

* Add missing docs for timeout exceptions

* Add info on auth failures
This commit is contained in:
Atul Mohan 2020-11-13 08:45:40 -06:00 committed by GitHub
parent c3cad461bc
commit 21e3c4b39c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/querying/querying.md
View File

@ -107,7 +107,7 @@ curl -X DELETE "http://host:port/druid/v2/abc123"
## Query errors
If a query fails, you will get an HTTP 500 response containing a JSON object with the following structure:
If a query fails, Druid returns a response with an HTTP response code and a JSON object with the following structure:
```json
{
@ -117,9 +117,14 @@ If a query fails, you will get an HTTP 500 response containing a JSON object wit
"host" : "druid1.example.com:8083"
}
```
The HTTP response code returned depends on the type of query failure. For timed out queries, an HTTP 504 response code is returned.
For [secured](../design/auth.md) Druid clusters, query requests respond with an HTTP 401 response code in case of an authentication failure. For authorization failures, an HTTP 403 response code is returned.
If a query request fails due to being limited by the [query scheduler laning configuration](../configuration/index.md#broker), an HTTP 429 response with the same JSON object schema as an error response, but with `errorMessage` of the form: "Total query capacity exceeded" or "Query capacity exceeded for lane 'low'".
For every other type of query failures, an HTTP 500 response code is returned.
The fields in the response are:
|field|description|