Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qdrant: Add named_vector functionality to haystack Integration #1226

Open
rlnrbio opened this issue Nov 29, 2024 · 0 comments
Open

Qdrant: Add named_vector functionality to haystack Integration #1226

rlnrbio opened this issue Nov 29, 2024 · 0 comments
Labels
feature request Ideas to improve an integration P2

Comments

@rlnrbio
Copy link

rlnrbio commented Nov 29, 2024

Hi,

are there any plans to integrate the capability of storing and querying multiple vectors for each point in qdrant beyond Sparse Vectors? Especially in the multimodal world this is quite an important feature and I currently can't use it w/ haystack.

Previously, if you wanted to use semantic search with multiple vectors per object, you had to create separate collections for each vector type. This was even if the vectors shared some other attributes in the payload. With Qdrant 0.10, you can now store all of these vectors together in the same collection, which allows you to share a single copy of the payload. This makes it easier to use semantic search with multiple vector types, and reduces the amount of work you need to do to set up your collections.

@rlnrbio rlnrbio added the feature request Ideas to improve an integration label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Ideas to improve an integration P2
Projects
None yet
Development

No branches or pull requests

2 participants