lance-format / lance-format/lance
Thread MemoryPool through FTS / inverted index build
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
Replace the bespoke per-worker memory watermark (default 2 GB) in the FTS / inverted index build with a MemoryReservation drawn from the per-build MemoryPool. Flush posting-list segments when try_grow returns Err rather than at the private watermark.
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 with the FTS and inverted-index build entry points and inspect how the per-build MemoryPool, MemoryReservation, and posting-list flushing are currently connected; issue #7301 provides broader context. Done means the private per-worker watermark is replaced, try_grow errors trigger segment flushing, and the build remains bounded by its MemoryPool.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- search
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100