feat: Qdrant Vector Database #81
Open
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
Closed
|
Looked into implementing qdrant async client Would we still want to retain support for sync qdrant? Would restructure code that we have, but have two separate vector-DB. |
|
Hoping we can get some more traction on this given the benfits of Qdrant over pgvector over other solutions. |
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.
Qdrant vector database supported. Added section in readme in setting up Qdrant environmental variables as well as specifically running docker image. Implemented Async methods for qdrant.
Tested using bedrock with
amazon.titan-embed-text-v2:0with all 3 supported currently vector databases (pgvector, qdrant, and atlas mongo)Tested
/ids,/documents,/delete,/embed,/queryand/query_multipleendpoints successfully with qdrant, pgvector, and atlas mongo.