-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Throw nicer exception in SpanBooleanQueryRewriteWithMaxClause #126387
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
Merged
iverase
merged 3 commits into
elastic:main
from
iverase:SpanBooleanQueryRewriteWithMaxClause
Apr 8, 2025
Merged
Throw nicer exception in SpanBooleanQueryRewriteWithMaxClause #126387
iverase
merged 3 commits into
elastic:main
from
iverase:SpanBooleanQueryRewriteWithMaxClause
Apr 8, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
john-wagster
approved these changes
Apr 7, 2025
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
💔 Backport failed
You can use sqren/backport to manually backport by running |
iverase
added a commit
to iverase/elasticsearch
that referenced
this pull request
Apr 8, 2025
…c#126387) Throw an ElasticsearchStatusException with a RestStatus.BAD_REQUEST code instead of a generic RuntimeException. # Conflicts: # server/src/main/java/org/elasticsearch/common/lucene/search/SpanBooleanQueryRewriteWithMaxClause.java
elasticsearchmachine
pushed a commit
that referenced
this pull request
Apr 8, 2025
…126387) (#126439) * Throw nicer exception in SpanBooleanQueryRewriteWithMaxClause (#126387) Throw an ElasticsearchStatusException with a RestStatus.BAD_REQUEST code instead of a generic RuntimeException. # Conflicts: # server/src/main/java/org/elasticsearch/common/lucene/search/SpanBooleanQueryRewriteWithMaxClause.java * iter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport
Automatically create backport pull requests when merged
backport pending
>non-issue
:Search Relevance/Search
Catch all for Search Relevance
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
v8.19.0
v9.1.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This class throws an error if more than
maxExpansions
terms are found andhardLimit
is set. The current error thrown is a RuntimeEception which Elasticsearch cannot handle. This commit proposes to change it to an exception that can be handle by Elasticsearch. More over, the rest status of such a request should be different to 500 as this is expected for such a request.We are proposing to throw an
ElasticsearchStatusException
with a RestStatus.BAD_REQUEST code.