-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Document changes in partial result reporting #124928
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -63,6 +63,11 @@ You can also specify a format using the `Accept` HTTP header. If you specify | |
both this parameter and the `Accept` HTTP header, this parameter takes | ||
precedence. | ||
|
||
`allow_partial_results`:: | ||
(Optional, boolean) If `true`, partial results will be returned if there are shard failures, but | ||
the query can continue to execute on other clusters and shards. This defaults to the value of | ||
the setting `esql.query.allow_partial_results`. | ||
|
||
[discrete] | ||
[role="child_attributes"] | ||
[[esql-query-api-request-body]] | ||
|
@@ -120,11 +125,17 @@ returned if `drop_null_columns` is sent with the request. | |
(array of arrays) | ||
Values for the search results. | ||
|
||
`is_partial`:: | ||
(boolean) | ||
Indicates whether the response is partial. Partial responses can happen due to failures in remote clusters | ||
smalyshev marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
or single shards, or stopping an async query. | ||
|
||
`_clusters`:: | ||
(object) | ||
Metadata about clusters involved in the execution of a cross-cluster query. Only returned (1) for | ||
cross-cluster searches and (2) when `include_ccs_metadata` is sent in the body and set to `true` | ||
and (3) when `format` of the response is set to JSON (the default), CBOR, SMILE, or YAML. | ||
Metadata about clusters involved in the execution of a query. This field is present in the response in the following cases: | ||
(1) for cross-cluster searches, when `include_ccs_metadata` is sent in the body and set to `true`; | ||
(2) the result is partial (`is_partial` is `true`) and there are failures on some clusters. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Question: if all shards were successful in the local cluster, will the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, if there are any failures that make the response partial, then There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Question: metadata would be present if the query is stopped, right? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, unless there are any failures, it's one of 1) include_ccs_metadata + CSS; or 2) partial + failures. If there are no failures to report then 2) is not activated. |
||
It is only returned if the `format` of the response is set to JSON (the default), CBOR, SMILE, or YAML. | ||
See <<ccq-cluster-details>> for more information. | ||
|
||
`profile`:: | ||
|
Uh oh!
There was an error while loading. Please reload this page.