Skip to content

Fix npe when using source confirmed text query against missing field #127414

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

benwtrent
Copy link
Member

We should check for the field and statistics actually existing when checking matches and explanation with match_only_text fields

closes: #125635

@benwtrent benwtrent added >bug auto-backport Automatically create backport pull requests when merged :Search Relevance/Search Catch all for Search Relevance v8.18.1 v8.19.0 v9.1.0 labels Apr 25, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch label Apr 25, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search-relevance (Team:Search Relevance)

@elasticsearchmachine
Copy link
Collaborator

Hi @benwtrent, I've created a changelog YAML for you.

Copy link
Contributor

@john-wagster john-wagster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@benwtrent benwtrent added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Apr 25, 2025
@elasticsearchmachine elasticsearchmachine merged commit 3d67e0e into elastic:main Apr 29, 2025
17 checks passed
@benwtrent benwtrent deleted the bugfix/address-source-confirmed-npe branch April 29, 2025 17:05
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.18 Commit could not be cherrypicked due to conflicts
8.19 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 127414

@benwtrent
Copy link
Member Author

It doesn't need to be backported to v8.18/19 as those didn't suffer from this bug as it was introduced with the scoreSupplier pattern in Lucene 10.

@benwtrent
Copy link
Member Author

💚 All backports created successfully

Status Branch Result
9.0

Questions ?

Please refer to the Backport tool documentation

benwtrent added a commit to benwtrent/elasticsearch that referenced this pull request Apr 29, 2025
…lastic#127414)

We should check for the field and statistics actually existing when
checking matches and explanation with `match_only_text` fields

closes: elastic#125635
(cherry picked from commit 3d67e0e)
elasticsearchmachine pushed a commit that referenced this pull request Apr 29, 2025
…127414) (#127526)

We should check for the field and statistics actually existing when
checking matches and explanation with `match_only_text` fields

closes: #125635
(cherry picked from commit 3d67e0e)
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 auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport pending >bug :Search Relevance/Search Catch all for Search Relevance Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch v9.0.1 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Highlight of SourceConfirmedTextQuery can throw NPE
4 participants