Why Qdrant generated ID policy must be UUID
lifejwang11 opened this issue · comments
Please do a quick search on GitHub issues first, there might be already a duplicate issue for the one you are about to create.
If the bug is trivial, just go ahead and create the issue. Otherwise, please take a few moments and fill in the following sections:
Bug description
A clear and concise description of what the bug is about.
Why Qdrant generated ID policy must be UUID
Environment
Please provide as many details as possible: Spring AI version, Java version, which vector store you use if any, etc
0.8.1
Steps to reproduce
Steps to reproduce the issue.
Expected behavior
A clear and concise description of what you expected to happen.
Minimal Complete Reproducible example
Please provide a failing test or a minimal complete verifiable example that reproduces the issue.
Bug reports that are reproducible will take priority in resolution over reports that are not reproducible.
Qdrant only allows UUIDs and +ve integers as point IDs.
https://qdrant.tech/documentation/concepts/points/#point-ids
Qdrant only allows UUIDs and +ve integers as point IDs. https://qdrant.tech/documentation/concepts/points/#point-ids
so why only support one?I think support all. Id is also need.can I try and commit PR?
Could you please explain? I didn't get what you meant.
Could you please explain? I didn't get what you meant.
I want to use number as IDs, but i find no way
Right.
At the time, if I remember correctly, the interface restricted IDs to strings. So, only UUIDs(String) were supported.
Right.
At the time, if I remember correctly, the interface restricted IDs to strings. So, only UUIDs(String) were supported.
Can support number in the future?Or can I modify code to support it?
Contributions are always accepted if they add value.
Yeah, that was the interface we had to work with.
Hi @lifejwang11 , can't you just convert the int ID into a String?
Maybe I'm not seeing the reasons why this won't be sufficient?
@tzolov, it's because of
#602 (comment)