Repository navigation
fix(qdrant): add explicit BM25 sparse upgrade - #452
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Collaborator
Author
|
Validation evidence for final head
Coverage contract: non-raw points are ready only when they are exactly one of |
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.
What changed
plan_qdrant_bm25_upgrade()and explicitupgrade_qdrant_bm25(writers_stopped=True)SDK APIsand
query_points(using="bm25")performs native sparse retrievalbm25vector in bounded batchesL1_RAW_hy_memory_bm25_state=empty, without searchable sentinels or sidecar stateIDFmodifier used by FastEmbedQdrant/bm25partial remote failures as structured states
Safety
Verification
uv lock --checkenvironment-gated and run in CI against Qdrant Server 1.18
thread preserved
non-IDF delete/recreate, empty-document coverage and native keyword retrieval
keyword_searchreturned the unique markerNot in this PR
Official Qdrant contract
Qdrant 1.18+ supports adding named sparse vectors to an existing collection;
existing points must then be populated:
https://qdrant.tech/documentation/manage-data/collections/#update-vector-schema