feat(fts): define global BM25 statistics wire contract - #8938
Open
zhangstar333 wants to merge 2 commits into
Open
feat(fts): define global BM25 statistics wire contract#8938zhangstar333 wants to merge 2 commits into
zhangstar333 wants to merge 2 commits into
Conversation
Contributor
There was a problem hiding this comment.
✅ Gate recommendation: approve.
The current revision addresses both prior findings: V1 now fails closed for cross-corpus leaves and explicitly assigns same-query attachment to the trusted planner. The single-corpus wire scope matches #8937, and the schema/build integration compiles cleanly.
Author
|
@Xuanwo hi, could you please have a look at this pr when you are free, very Thanks! |
This was referenced Sep 2, 2026
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.
Distributed FTS executors need one query-bound, corpus-wide BM25 statistics payload so workers searching different index segments can produce comparable scores.
This is part of #8937 and supports the downstream Doris use case described in apache/doris#67435.