doc: Design catalog-driven cluster lifecycle - #38694
Closed
aljoscha wants to merge 1 commit into
Closed
Conversation
Define catalog authority for maintained lifecycle and separate it from request-scoped query execution. Record the ownership and readability boundaries needed for independent clients, while leaving implementation mechanisms open and full multi-adapter operation outside this deliverable. Include an append-only implementation log for work across sessions.
Contributor
Author
|
Replaced by #38696, Decoupled coordination. The document and branch names now describe the architectural outcome rather than the catalog-driven mechanism. The agreed scope and contracts are unchanged. |
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
1 participant
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.
Motivation
Decouple maintained storage and compute lifecycle from the adapter that initiated it. Catalog state should supply lifecycle authority, while independent query clients use a separate fast protocol.
Description
Add a minimal design and an append-only implementation log as the handoff for iterative implementation sessions. The design records ownership, readability, recovery, and query-ordering boundaries without prescribing catalog fields, protocol messages, or process topology.
Full multi-adapter operation remains the destination, not the immediate deliverable. Query-local dataflows stay on the fast protocol, and transparent query or session failover is out of scope. Completing the relevant catalog implication paths is included where needed.
This draft is the working PR for following the design and its implementation. It currently contains only the design document and makes no user-visible behavior changes.
Verification
No tests are added or modified because this is documentation only. The design calls for existing CI, nightly, and performance coverage, with targeted coverage for changed boundaries where needed during implementation.