ES|QL: Make FUSE available in release builds #135603
Merged
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
ioanatia
added
>feature
Team:Search - Relevance
|
Hi @ioanatia, I've created a changelog YAML for you. |
elasticsearchmachine
added
Team:Search Relevance
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
carlosdelest
approved these changes
Sep 29, 2025
There was a problem hiding this comment.
LGTM. Nice adding the L2_NORM as a different capability.
In this PR or in a follow up, we can clean up the references to FUSE_V6 capability in the Analyzer, StatementParser, Verifier, FieldNameUtils tests, as it will be available both in release and snapshot builds and are unnecessary.
This was referenced Sep 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
tracked in #123389
One thing to note is that L2_NORM score normalization support will continue to be in snapshot.
We still support minmax as a score normalization method which will be the most used.
The reason why we keep L2_NORM in snapshot is because we still need to decide on what would be the best behaviour when the scores are negative (which is not a problem we have with DSL).