XiaoHongbo-Hope opened a new pull request, #614: URL: https://github.com/apache/paimon-rust/pull/614
`SearchResult::top_k` only sorted by score on the truncation path (candidates > k). When `k >= candidate count`, it returned rows in the unordered scored-map / insertion order instead of by relevance. This went unnoticed because the row order was previously discarded downstream (row-range scans re-read in file order); but consumers that honor the row order — e.g. the DataFusion `vector_search` scan — then get **unranked** results whenever `limit >= number of matched rows`. Affects `vector_search`, `full_text_search`, and `hybrid_search`. **Fix**: sort the no-truncation branch by relevance rank too, and update the unit tests that asserted the old insertion-order behavior. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
