[python] Execute hybrid search routes concurrently - #9797
Open
TheR1sing3un wants to merge 1 commit into
Open
TheR1sing3un wants to merge 1 commit into
TheR1sing3un wants to merge 1 commit into
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
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.
Purpose
Hybrid search executes independent vector and full-text routes sequentially before ranking their results. Execute multiple routes concurrently with a bounded four-worker pool, then convert results in route order so RRF, weighted-score, and MRR ranking semantics remain unchanged.
Empty and single-route searches keep the direct path. On failure, pending work is cancelled, started routes are allowed to clean up, and the original route exception is propagated.
Tests
python -m pytest -q pypaimon/tests/hybrid_search_execution_test.py pypaimon/tests/hybrid_search_ranker_test.py: 10 passed.git diff --checkpassed.Benchmark
macOS arm64, Python 3.9.6. Each route uses a simulated I/O delay; values are medians of 12 runs. This isolates route scheduling from index implementation and ranking cost.
Results remained in route order in every run. Real query gains depend on route latency distribution and nested native-index parallelism. The temporary benchmark driver is not included in the change.