feat: Support for vector search with Qdrant#111
Open
Anush008 wants to merge 1 commit into
Open
Conversation
|
@Anush008 is attempting to deploy a commit to the andylizf's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
Description
This PR adds an alternative vector search backend to PixelRAG.
Qdrant is an open-source vector search engine built for high performance and large-scale workloads. Users can opt into Qdrant to take advantage of quantization, disk-backed vectors and more.
The Qdrant client dependency is installed on demand(
pip install 'pixelrag[qdrant]). FAISS remains the default backend, so existing users will see no change in behavior.The PR introduces a
class VectorBackend(Protocol)abstraction. It enables any provider like FAISS and Qdrant to power PixelRAG's vector search.Setup
You can run Qdrant with
Then follow the instructions in the
README.md. The Qdrant dashboard will be accessible at http://localhost:6333/dashboard.Testing
I've tested the implementation against a local Qdrant instance.