Store temporal update counts (t_len on Node/Edge storage) as metadata
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
Store EdgeStorageInner/NodeStorageInner::t_len() as metadata to avoid scanning all segments when loading a graph, this is needed to know where to continue from for future event ids. The correct place to store this information seems to be LayerStats.
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
Start with EdgeStorageInner::t_len(), NodeStorageInner::t_len(), and LayerStats to trace how temporal update counts are currently derived while loading a graph. Store the counts as metadata in LayerStats so loading avoids scanning all segments and future event IDs can continue from the correct position.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100