tursodatabase / tursodatabase/libsql
"vector_top_k" with duplicated vectors
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Hey everyone!
I have a little database that I use for semantic search.
I only embed a subset of the text which means that some embedding can be duplicated.
Without the index, I can access them without any issue, but with libsql_vector_idx, only one of the row is returned. I guess that only one rowid can be stored per vector.
Any idea how I can solve that (except adding a little bit of noise?)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior with duplicated embeddings, comparing vector_top_k without an index against libsql_vector_idx. Inspect those entry points to determine how duplicate vectors are handled; done means every matching row is returned when embeddings are identical, without requiring added noise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100