Vector search results are inaccurate after creating an asynchronous index
Open
Nobody has claimed this yet.
dima
type: bug
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Environment
- Version: Starting seekdb (OceanBase seekdb) source revision 1-f8501118d6eca3ee5c2714151d0a5cf842726dcb.seekdb (OceanBase seekd...)
Description
After creating an asynchronous or synchronous index, the results returned by vector search queries are inaccurate.
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
No file or test is named in the issue. Start by reproducing vector search queries after creating both asynchronous and synchronous indexes, then compare their returned results with the expected matches. Done means indexed vector searches return accurate results in both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100