lance-format / lance-format/lance
Thread MemoryPool through scalar (btree/bitmap) index build
Open
Nobody has claimed this yet.
A-index
performance
rust
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
Thread the per-build MemoryPool through the scalar btree/bitmap builds. These are small today; the goal is uniform accounting and a clean spill signal consistent with the other families.
Part of #7301.
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 by tracing the scalar btree and bitmap index build paths, then compare them with the other index families that already thread a per-build MemoryPool. Done means both builds use the pool for uniform accounting and expose a consistent spill signal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100