Generation handling for the vector indexes needs work
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
- error handling picks generation 0 on any failure to read the metadata which might cause problems, that should only happen if the metadata file doesn't exist
- old generation should be cleaned up on success, not left behind
- Multiple simultaneous calls to reindex a graph need to be handled properly, right now they simply race and might thus overwrite a newer index
Originally posted by @ljeub-pometry in https://github.com/Pometry/Raphtory/pull/2705#discussion_r3829385320
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
Locate the vector-index generation metadata handling and graph reindex entry points. Trace read failures, successful replacement, and simultaneous reindex calls; done means only missing metadata selects generation 0, old generations are cleaned up after success, and concurrent calls cannot overwrite a newer index.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100