Execute completed cohorts at every materialized maintenance frontier - #665
Merged
Merged
Conversation
zzylol
changed the base branch from
feat/maintenance-cohort-publication
to
main
September 11, 2026 18:44
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.
Why
A synchronized immutable input cohort needs to execute each installed materialized frontier without reusing the first source's state.
What
Teach the existing registry and completed-input entry point to consume one complete population per source definition at matching full windows.
How
One Live/Frozen input representation resolves each bound definition. The cohort entry validates the exact source map, common labels, shared window contract, and each source's finite singleton proof before computing or recovering output. It uses the existing full-cohort lineage and atomic publication transaction.
Before this PR
Execution supplied one source to every eligible materialized input.
After this PR
A bound two-source operator graph can merge exact sums, finalize, and update its configured sketch with all inputs. Single-source execution delegates to the same entry point.
Verification
12 actual-sketchlib-139 maintenance tests passed. A bound operator fixture computes 2 + 7 = 9 through SumMerge→Finalize→KLL, rejects execution before closure without output, publishes once, and does not add parts on retry or restart. This fixture is not a frontend selection or performance claim.
Limits
Automatic installation/scheduling still retains its single-source gate pending a real selected-plan integration. Multiple populations per frontier, cross-group routing, continuous watermarks, and sliding execution remain later work. Includes the already-reviewed shared window helper from #661; depends on #662 and #664.