Qdrant: add migration utility function for Sparse Embedding support #659
Conversation
This file contains 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
github-actions
bot
added
type:documentation
anakin87
commented
Apr 12, 2024
Comment on lines
-8
to
-9
| "haystack_integrations.document_stores.qdrant.converters", | ||
| "haystack_integrations.document_stores.qdrant.filters", |
There was a problem hiding this comment.
unrelated. I think these should not be user-facing
masci
approved these changes
Apr 12, 2024
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.
Add a utility function to migrate an existing
QdrantDocumentStoreto a new one with support for sparse embeddings.Related to #578
Inspired by @lambda-science's migration script reported in #578 (comment)
Applies to on-premise and cloud instances of Qdrant but does not work for local in-memory/disk-persisted instances.
I tested it locally with 10K documents.
Since our tests are based on memory instances of Qdrant, to test the migration function in the CI,
we should rework our testing suite introducing Docker.