Is your feature request related to a problem? Please describe.
For many use scenarios, users simply treat each entity as a embedding list.
For example, under chatPDF use cases, each PDF is split into chunks, and each chunk embedded into a vector.
It would be similar to agent scenario, where each agent has limited vectors.
In that case, we build index for each entities, not for the whole segment.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
For many use scenarios, users simply treat each entity as a embedding list. For example, under chatPDF use cases, each PDF is split into chunks, and each chunk embedded into a vector. It would be similar to agent scenario, where each agent has limited vectors.
In that case, we build index for each entities, not for the whole segment.
Data model
Primary Key -> DocID Partition Key -> UserID Scalars -> Type, Author .... Vector -> Array [Chunk embeddings]
Search:
Describe the solution you'd like.
Describe an alternate solution.
No response
Anything else? (Additional Context)
No response