- Notifications
You must be signed in to change notification settings - Fork 25.5k
ES|QL: Make skip_unavailable catch all errors #128163
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
Conversation
Hi @smalyshev, I've created a changelog YAML for you. |
Hi @smalyshev, I've updated the changelog YAML for you. Note that since this PR is labelled |
Pinging @elastic/es-analytical-engine (Team:Analytics) |
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
Hi @smalyshev, I've updated the changelog YAML for you. Note that since this PR is labelled |
Hi @smalyshev, I've updated the changelog YAML for you. Note that since this PR is labelled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks Stas!
💔 Backport failed
You can use sqren/backport to manually backport by running |
@smalyshev according to this PR's labels, I need to update the changelog YAML, but I can't because the PR is closed. Please either update the changelog yourself on the appropriate branch, or adjust the labels. Specifically:
|
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
* Make skip_unavailable catch all errors (cherry picked from commit 8484b71) # Conflicts: # x-pack/plugin/esql/src/main/java/org/elasticsearch/xpack/esql/plugin/ClusterComputeHandler.java
This is a reversal of the decision in #120236, now skip_unavailable is again catching all errors, like
_search
.