Repository navigation
feat(wal): advance catalog cursors after source closure - #424
Merged
Merged
Conversation
40 of 47 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
After a managed Lance publication closes its source pins, the catalog still retains the pending plan and prepared descriptors, preventing the next publication. Add
AdvancePublicationto atomically advance each selected source's checkpoint after verifying all signed source-quorum closure proofs, then release those dependencies.A bounded completion receipt preserves exact retries after publisher takeover, a newer pending plan, and checkpoint/restart. Table checkpoint frames preserve their legacy bytes before the first advancement and use a tagged extension afterward. Upgrade every replica before submitting the new command; advanced directories and the extended public
Tablequery encoding do not support older readers. This change performs no physical file or object deletion.Refs #378.
Testing