Vector index remains usable after deletion during refresh process
Open
Nobody has claimed this yet.
dima
type: bug
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 342
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 53
Description
Environment
- Version: 5.7.25 OceanBase seekdb (r) (Built 1-237f9a94e11e00b6616f19...)
Description
During a refresh operation, a vector index that has been deleted is still accessible and usable.
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 source files, tests, or entry points are named. Start by reproducing the refresh operation while deleting a vector index in seekdb 5.7.25, then trace the refresh and index-deletion paths. Done means a deleted vector index is no longer accessible or usable after refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100