-
Notifications
You must be signed in to change notification settings - Fork 846
fix(index): skip unrecognized index types #8529
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
Merged
Changes from 9 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
e6643d7
fix(index): skip unrecognized index types
lance-gatefixer[bot] 0312734
Merge origin/main into gatekeeper/fix-8528-1
lance-gatefixer[bot] a20e8ac
fix: validate complete index detail type identities
lance-gatefixer[bot] 1b3ac91
fix: preserve v0.36 scalar detail aliases
lance-gatefixer[bot] c86443b
Merge remote-tracking branch 'origin/main' into gatekeeper/fix-8528-1
lance-gatefixer[bot] 47fd703
Merge remote-tracking branch 'origin/main' into gatekeeper/fix-8528-1
lance-gatefixer[bot] 542e4d2
fix(index): apply reader boundary to maintenance
lance-gatefixer[bot] 45aab22
Merge branch 'main' into gatekeeper/fix-8528-1
Xuanwo c637af8
Merge remote-tracking branch 'origin/main' into gatekeeper/fix-8528-1
lance-gatefixer[bot] 13c32ea
Merge branch 'main' into gatekeeper/fix-8528-1
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
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.
The exact-name set now drops a released reader identity: the checked-in 0.36 fixture stores
/lance.index.pb.BTreeIndexDetails, while this registry records only the currentlance.table.BTreeIndexDetails. Current plugin lookup still resolves that fixture toBTree, butindex_type_is_knownreturns false, sooptimize_indices()skips a readable stable-format index. Register the exact historicallance.index.pbscalar identities alongside the current names (still case-insensitively), and cover the checked-in fixture.Reproducer
Add this test beside the index tests and run
cargo test -p lance --lib test_v036_scalar_details_are_still_known:Expected: the released identity is recognized because its reader is present. Observed on this head: the final assertion fails.
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.
Addressed in 1b3ac91. The registry now accepts the six exact scalar detail identities released under lance.index.pb in 0.36, and the checked-in BTree fixture confirms they remain known while unrelated namespaces stay rejected.
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 1b3ac910d: the checked-in 0.36 BTree fixture is recognized again, and all six released scalar aliases are registered without reopening suffix-based namespace matching.