-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add properties to a collection #3957
Comments
Hey @Waffleboy, could you please describe your use-case a bit more - why would you need those values collection-wide? Also, would it be possible to use special collection which would hold per-collection info instead? |
Hi @generall , There are some metadata we want to add to the table, for example which is the main date column to filter by. |
Ok, have you considered making another collection with collection-level-metadata? It seems that you would need to make 2 requests to the service to make this filtering requests anyway |
How would that work? The collection has one row with the payload being the collection-level-metadata? Rows need a vector, so some dummy vector? Seems very inelegant, and there wouldnt be a duplicate call as Im already calling |
Yes.
You can configure any vector size, and upload a point with a
It is, but its what is already supported in our current releases. Since we've seen requests for this multiple times, it's something we might add later down the line. But currently we have higher priority tasks to focus on, so it's not on our road map in the short term. |
you can actually configure no vectors at all. |
tbh, I don't see any advantages of the per-collection meta. Maybe you could provide a sample usage with "pseudocode" of how you would expect it to work |
I have a similar situation of @Waffleboy, we as a team work with multiple embedding models and store vectors into collection, it would be helpful if we could store collection metadata like embedding model, dimensions, and other details like description, data title etc., right now we are dealing the situation as recommended by @generall, it would be helpful if we store the metadata along with its vectors.
|
Whatever, we can make it as a separate text field and alter via collection update API. /bounty $100 |
💎 $100 bounty • QdrantSteps to solve:
Thank you for contributing to qdrant/qdrant! Add a bounty • Share on socials
|
helps in providing table metadata
/attempt #3957
|
💡 @abhishek818 submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
helps in providing table metadata or properties
helps in providing table metadata or properties
helps in providing table metadata or properties
Could I try my hand at this issue? @abhishek818 @generall |
Is your feature request related to a problem? Please describe.
If theres any information that applies table-wide, theres currently no way to add it in unless we add it as a metadata to every row. This causes space wastage
Describe the solution you'd like
Ability to add any properties to the table. eg,
Describe alternatives you've considered
Currently adding as a column metadata instead (so every row has a static value)
Additional context
The text was updated successfully, but these errors were encountered: