Support partial results in ES|QL #122802
Assignees
Labels
:Analytics/ES|QL
AKA ESQL
>enhancement
Meta
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Comments
elasticsearchmachine
added
the
Team:Analytics
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
|
Related: #111518 |
2 tasks
This was referenced Mar 4, 2025
dnhatn
added a commit
that referenced
this issue
Mar 5, 2025
This change introduces a cluster setting `esql.query.allow_partial_results` that allows enabling or disabling allow_partial_results in ES|QL at the cluster-wide level. Initially, this setting defaults to false, but it will be switched to true soon. The reason for not changing the default in this PR is that it requires adjusting many tests, which would make the PR too large. Instead, we will adjust the tests incrementally and switch the default when the tests are ready. This cluster setting is useful for falling back to the previous behavior (i.e., disabling allow_partial_results) if users upgrade to the new version and haven't updated their queries. Also, the default setting can be overridden on a per-request basis via a URL parameter (allow_partial_results) (changed from request body to URL parameter to conform to the proposal). Relates #122802
dnhatn
added a commit
to dnhatn/elasticsearch
that referenced
this issue
Mar 5, 2025
This change introduces a cluster setting `esql.query.allow_partial_results` that allows enabling or disabling allow_partial_results in ES|QL at the cluster-wide level. Initially, this setting defaults to false, but it will be switched to true soon. The reason for not changing the default in this PR is that it requires adjusting many tests, which would make the PR too large. Instead, we will adjust the tests incrementally and switch the default when the tests are ready. This cluster setting is useful for falling back to the previous behavior (i.e., disabling allow_partial_results) if users upgrade to the new version and haven't updated their queries. Also, the default setting can be overridden on a per-request basis via a URL parameter (allow_partial_results) (changed from request body to URL parameter to conform to the proposal). Relates elastic#122802
elasticsearchmachine
pushed a commit
that referenced
this issue
Mar 5, 2025
This change introduces a cluster setting `esql.query.allow_partial_results` that allows enabling or disabling allow_partial_results in ES|QL at the cluster-wide level. Initially, this setting defaults to false, but it will be switched to true soon. The reason for not changing the default in this PR is that it requires adjusting many tests, which would make the PR too large. Instead, we will adjust the tests incrementally and switch the default when the tests are ready. This cluster setting is useful for falling back to the previous behavior (i.e., disabling allow_partial_results) if users upgrade to the new version and haven't updated their queries. Also, the default setting can be overridden on a per-request basis via a URL parameter (allow_partial_results) (changed from request body to URL parameter to conform to the proposal). Relates #122802
georgewallace
pushed a commit
to georgewallace/elasticsearch
that referenced
this issue
Mar 11, 2025
This change introduces a cluster setting `esql.query.allow_partial_results` that allows enabling or disabling allow_partial_results in ES|QL at the cluster-wide level. Initially, this setting defaults to false, but it will be switched to true soon. The reason for not changing the default in this PR is that it requires adjusting many tests, which would make the PR too large. Instead, we will adjust the tests incrementally and switch the default when the tests are ready. This cluster setting is useful for falling back to the previous behavior (i.e., disabling allow_partial_results) if users upgrade to the new version and haven't updated their queries. Also, the default setting can be overridden on a per-request basis via a URL parameter (allow_partial_results) (changed from request body to URL parameter to conform to the proposal). Relates elastic#122802
dnhatn
added a commit
that referenced
this issue
Mar 16, 2025
This change includes failures when ESQL returns partial results. It also carries failures between cluster requests. Relates #122802
dnhatn
added a commit
to dnhatn/elasticsearch
that referenced
this issue
Mar 17, 2025
This change includes failures when ESQL returns partial results. It also carries failures between cluster requests. Relates elastic#122802
dnhatn
added a commit
that referenced
this issue
Mar 17, 2025
This change includes failures when ESQL returns partial results. It also carries failures between cluster requests. Relates #122802
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Support partial results in each cluster: Support partial results in ES|QL #121942
Support partial results across clusters: Support partial results in CCS in ES|QL #122708
Return shard-level failures (currently only returning the
is_partialflag) Report failures on partial results #124823 Include failures in partial response #124929Return fatal/non-fatal errors in data node responses to enable retries (or one shard at the time?)
Introduce
esql.query.allow_partial_resultssetting: Introduce allow_partial_results setting in ES|QL #122890Defaults to true
Add documentation
Handle partial_results in the final reduction
Allow partial results during resolution
The text was updated successfully, but these errors were encountered: