-
Notifications
You must be signed in to change notification settings - Fork 834
fix(index): keep an index this build cannot read out of the erase path #8427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Xuanwo
merged 11 commits into
lance-format:main
from
wombatu-kun:fix/unsupported-index-survives-commit
Aug 29, 2026
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
5459208
fix(index): keep an index this build cannot read out of the erase path
28fbc60
fix(index): route index bookkeeping and planning through the complete…
4b0ef74
docs(format): require writers to carry forward index segments they ca…
51b9775
docs(format): revert the writer-side carry-forward rule pending a PMC…
e2dc2e5
Fix build after rebase onto main
712b002
fix(index): defer compaction and reject mixed declarations around an …
61a4979
fix(index): reject a compaction that strands an index this build cann…
9e8e8fc
fix(index): reconstruct unreadable-index coverage in current fragment…
6c2807c
Merge branch 'main' into fix/unsupported-index-survives-commit
Xuanwo 852e393
Merge branch 'main' into fix/unsupported-index-survives-commit
7a05595
Merge branch 'main' into fix/unsupported-index-survives-commit
Xuanwo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Legacy no-bitmap coverage is returned here in its original fragment-ID space.
load_all_indicesapplies the fragment-reuse index only to storedSome(bitmap)values, so this reconstructed set never follows a prior deferred compaction. After deferred compaction maps fragments 0/1 to 2, the guard compares 0/1 against an eager rewrite of 2 and permits 2 to become 3; the future reader's reuse chain still ends at deleted fragment 2. Remap reconstructed coverage through the current fragment-reuse index before returning it, so both the planner and commit guard use current IDs.This is the current-head successor to the earlier discussion.
Reproducer
I added and ran this regression on the current head:
CARGO_TARGET_DIR=/home/agent/cache/cargo-target cargo test -p lance --lib gate_repro_legacy_unsupported_coverage_follows_the_reuse_chain -- --nocaptureObserved: the assertion failed with
mapped=RoaringBitmap<[2]>andlive=RoaringBitmap<[3]>.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done 9e8e8fc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 9e8e8fc: reconstructed legacy coverage now passes through the current fragment-reuse index before planner exclusion and commit validation. The focused regression passes and confirms that, after deferred compaction maps fragments 0/1 to 2, the commit boundary rejects rewriting fragment 2 and the default planner keeps it while compacting uncovered fragments.