Skip to content

Add support for includeNamedQueriesScore in Query#3243

Open
velizarvel wants to merge 2 commits intospring-projects:mainfrom
velizarvel:add-support-for-include-named-queries-score-in-query
Open

Add support for includeNamedQueriesScore in Query#3243
velizarvel wants to merge 2 commits intospring-projects:mainfrom
velizarvel:add-support-for-include-named-queries-score-in-query

Conversation

@velizarvel
Copy link

Elasticsearch 8.8 introduced the include_named_queries_score flag, allowing search responses to return score contributions for named queries. When enabled, the matched_queries field changes from List to Map<String, Double>.
This functionality is currently not accessible through higher-level abstractions such as ElasticsearchOperations.

Signed-off-by: veljko.potparic <veljko_velid@yahoo.com>
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 12, 2026
Signed-off-by: veljko.potparic <veljko_velid@yahoo.com>
@sothawo
Copy link
Collaborator

sothawo commented Feb 12, 2026

You deleted the comment template for the pull request, here again as a reminder:

- [ ] You have read the [Spring Data contribution guidelines](https://github.com/spring-projects/spring-data-build/blob/master/CONTRIBUTING.adoc).
- [ ] **There is a ticket in the bug tracker for the project in our [issue tracker](https://github.com/spring-projects/spring-data-elasticsearch/issues)**. Add the issue number to the _Closes #issue-number_ line below
- [ ] You use the code formatters provided [here](https://github.com/spring-projects/spring-data-build/tree/master/etc/ide) and have them applied to your changes. Don’t submit any formatting related changes.
- [ ] You submit test cases (unit or integration tests) that back your changes.
- [ ] You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

Closes #issue-number
  • You have not created an issue (first) describing the problem and how you plan to solve it.
  • You did not add tests, as you wrote that sending that new parameter with the query changes a field in the returned data, provide an integration test that shows that this is handled correctly and no existing behaviour is broken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: waiting-for-triage An issue we've not yet triaged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants