Repository navigation
feat(java): expose global BM25 statistics for FTS queries - #8822
zhangstar333 wants to merge 6 commits into
Conversation
|
Important This PR touches the Lance format specification. Substantive changes to the format specification — the If this is a meaningful format change:
|
|
Important Format specification voteThis PR modifies the Lance format specification, so it requires 3 binding +1 votes from PMC members (excluding the proposer) and a minimum 72-hour voting period, weekends excluded, before it can merge. Vote by approving this PR (+1) or requesting changes (−1, a veto). See the voting process. Status: ❌ Blocked — 0 of 3 required approvals
Updated automatically by the format-spec vote gate, which re-checks every 15 minutes — just voted? Re-check now (press Run workflow; leave the input blank to re-check every open format PR). A PMC member may apply the |
There was a problem hiding this comment.
The rebase preserves the producer behavior and adds explicit cross-column rejection coverage. V1 now makes its trust boundary clear: a planner must attach the payload only to the query that produced it because consumers cannot independently verify source-query identity.
That leaves a bounded correctness risk if a trusted planner misbinds the payload. The downstream validation of independently checkable snapshot, index, and segment metadata, plus distributed Top-K equivalence tracked by #8937, also remain outside this revision. No further producer change is requested here.
This is the implementation for #8937 and depends on #8938.
It supports the distributed FTS use case described in apache/doris#67435.