Repository navigation
feat(wal): retire bounded manifest history - #428
Merged
beinan merged 1 commit intoOct 21, 2026
Merged
Conversation
63 of 76 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The managed catalog retains a record for each selected Lance manifest and eventually reaches its bounded history limit. Add explicit retirement that keeps the bootstrap anchor and a contiguous suffix, while protecting the current head, pending plans, confirmed publications and the latest durable advancement receipt. This allows further publications without increasing the index capacity.
Retired version queries and reservation retries return a history boundary, including retries from an old publisher. That response does not authorize deleting the supplied immutable object. This retires catalog metadata only; object cleanup and production reader integration remain separate. All replicas must support retirement before it is enabled because older readers may reject the sparse history.
Refs #378.
Testing