lance-format / lance-format/lance
Materialize deletions when updating scalar indices
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
Description
When we update a scalar index we basically retrain it on the old data (which we scan from the old index, already sorted) and the new data (which we scan from the dataset, in sorted order). While we are scanning the old data we scan both the value column and the row id column. We can grab the deletion information for the affected fragments from the dataset and filter out rows based on the row id. This should allow us to relatively cheaply materialize deletions at the same time we run an update.
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 at the scalar index update path and trace how old index data and new dataset data are scanned. Check how deletion information for affected fragments can be used with row IDs; done means deletions are materialized during the update and deleted rows are filtered from the retraining input.
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
- 35/100