With this change, ES|QL will return partial results instead of failing
the entire query when encountering errors. Callers should check the
partial_results flag in the response to determine if the result is
partial or complete. If returning partial results is not desired, this
option can be overridden per request via the allow_partial_results
parameter in the query URL or globally via the cluster setting
esql.allow_partial_results.

Relates elastic#122802

This reverts commit 81555cc.

…126286)

This reverts commit 81555cc from
#125060.

Fix #126275

@idegtiarenko and I investigated and believe this needs reverting:
silently dropping results from the query response in case any index is
missing can lead to real problems if users don't spot their mistake. I'm
also not sure if all the results will get dropped, or only from some
nodes/shards/clusters, meaning that this might be hard to spot by users
if only some results get dropped.

The main PR has no transport version bump, no new ESQL capability, and
was merged 15h ago - so it should be safe to just revert it. I noticed
there was a linked Serverless PR on the original PR, but it merely
disabled some obsolete tests on Serverless and doesn't require reverting
itself.

With this change, ES|QL will return partial results instead of failing
the entire query when encountering errors. Callers should check the
partial_results flag in the response to determine if the result is
partial or complete. If returning partial results is not desired, this
option can be overridden per request via the allow_partial_results
parameter in the query URL or globally via the cluster setting
esql.allow_partial_results.

Relates elastic#122802

…)" (elastic#126286)

This reverts commit 81555cc from
elastic#125060.

Fix elastic#126275

@idegtiarenko and I investigated and believe this needs reverting:
silently dropping results from the query response in case any index is
missing can lead to real problems if users don't spot their mistake. I'm
also not sure if all the results will get dropped, or only from some
nodes/shards/clusters, meaning that this might be hard to spot by users
if only some results get dropped.

The main PR has no transport version bump, no new ESQL capability, and
was merged 15h ago - so it should be safe to just revert it. I noticed
there was a linked Serverless PR on the original PR, but it merely
disabled some obsolete tests on Serverless and doesn't require reverting
itself.

…tic#125060)" (elastic#126286)"

This reverts commit 8f38b13.

Restore changes from elastic#125060 now that
the breakage should be fixed.

* Revert "ESQL: Revert "Allow partial results by default in ES|QL (#125060)" (#126286)"

This reverts commit 8f38b13.

Restore changes from #125060 now that
the breakage should be fixed.

* Revert "ESQL: Revert "Allow partial results by default in ES|QL (elastic#125060)" (elastic#126286)"

This reverts commit 8f38b13.

Restore changes from elastic#125060 now that
the breakage should be fixed.

(cherry picked from commit eb479e5)

# Conflicts:
#	docs/release-notes/breaking-changes.md
#	x-pack/plugin/build.gradle
#	x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/plugin/ClusterComputeHandler.java

…127474)

* Allow partial results by default in ES|QL - Take 2 (#127351)

* Revert "ESQL: Revert "Allow partial results by default in ES|QL (#125060)" (#126286)"

This reverts commit 8f38b13.

Restore changes from #125060 now that
the breakage should be fixed.

(cherry picked from commit eb479e5)

# Conflicts:
#	docs/release-notes/breaking-changes.md
#	x-pack/plugin/build.gradle
#	x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/plugin/ClusterComputeHandler.java

* skip test

* fix test

* fix test