-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Add max_score to some Elasticsearch SearchHitsMetadata #233641
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
Closed
Closed
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
rudolf
approved these changes
Sep 1, 2025
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Contributor
|
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
Contributor
|
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
adcoelho
approved these changes
Sep 2, 2025
Member
Author
|
I discussed with the @elastic/devtools-team team that this is just too much work for Kibana. We're going to revert the PR in the specification. After all, we have lived without those required changes for years now. |
Contributor
💔 Build Failed
Failed CI Steps
Test Failures
Metrics [docs]
History
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
release_note:skip
Skip the PR/issue when compiling release notes
Team:actionable-obs
Formerly "obs-ux-management", responsible for SLO, o11y alerting, significant events, & synthetics.
Team:Fleet
Team label for Observability Data Collection Fleet team
Team:obs-ux-infra_services - DEPRECATED
DEPRECATED - Use Team:obs-presentation.
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.
elastic/elasticsearch-specification#1144 was opened in 2021 and just merged last week. It turns out that Elasticsearch search endpoint always returns
response.hits.hits._scoreandresponse.hit.max_score, so they are now required. It causes failures in Kibana type checks. This affects a lot of tests that have mock search responses.Since
_scoreandmax_scoreare already allowed today, the goal of this PR is to add them to the relevant tests so that making them actually required is less tedious.For example, an issue that I don't know how to fix is:
The affected lines:
kibana/x-pack/packages/ai-infra/product-doc-artifact-builder/src/tasks/extract_documentation.ts
Lines 43 to 58 in 3e02d88
I tried using
unknowninstead ofany, but then all accesses tosourcefail.