ES|QL: Set FUSE to execute on coordinator#135515
Merged
ioanatia merged 4 commits intoelastic:mainfrom Sep 26, 2025
Merged
Conversation
17 tasks
Collaborator
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
carlosdelest
approved these changes
Sep 26, 2025
Member
carlosdelest
left a comment
There was a problem hiding this comment.
This is nice. 👍
TIL about PipelineBreaker and ExecutesOn.
|
|
||
| ROW _id = ["a", "b", "c"], _score = 0.0, _index = "my_index", my_fork = "foo" | ||
| | MV_EXPAND _id | ||
| | LIMIT 10 |
Member
There was a problem hiding this comment.
Nit - I understand why this is needed, but probably makes no sense in practice. Maybe we can check that there's a ROW at the top and avoid the need for LIMIT in that case, as input will be already limited?
Member
Author
There was a problem hiding this comment.
I guess the usage of ROW is limited in practice, especially in combination with FUSE, but I added a note in #123389 and will definitely look into this as a follow up.
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
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
FUSE supports RRF and linear combination as the two method to assign new relevance scores.
FUSE cannot be pushed down to the data nodes, it needs to see the whole result set in order to assign new scores.
Because of this we need to:
ExecutesOn.CoordinatorandPipelineBreakertoFuseScoreEval.What this means practically is that the we are looking for another
PipelineBreakerexists before FUSE.