clockworklabs / clockworklabs/SpacetimeDB
Track index key ranges in view read sets
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
We currently track single index key lookups in a view's read set, but we treat range scans as full table scans which means if any row of the table is updated we must re-evaluate the view even if that row falls outside of the index key range that was used. We should also track index key ranges in the read set in the same way that we do single index keys.
Contributor guide
No contributing guide indexed for this repository
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. Start by locating the existing view read-set handling for single index key lookups, then compare how range scans are currently treated as full-table scans. Done means index key ranges are recorded and updates outside the used range no longer trigger view re-evaluation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100