Start maintenance DAG execution at supplied materializations - #615
Merged
Merged
Conversation
…ompute-materialized-frontier
…ompute-materialized-frontier # Conflicts: # data_plane/src/precompute_engine/maintenance_runtime.rs
zzylol
changed the base branch from
refactor/shared-precompute-plan-contract
to
main
September 11, 2026 00:23
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.
Ingest can already provide the state for a materialized SummaryAgg, but the maintenance scheduler still traversed its absorbed raw-input subtree first. A real ERP-selected KLL installation therefore failed on a Fallback node instead of storing its computed summary.
Add a materialized-input frontier to the generic operator registry. The scheduler validates placement and timing, then reuses the supplied state before visiting dependencies. Shared downstream branches reuse the same Arc. The production adapter resolves the frontier from the installed summary-definition binding; dependency/grouping checks also stop there.
Before:
Fallback → SummaryAgg → readouttried to execute Fallback even after ingest had computed SummaryAgg. After: maintenance starts from the supplied SummaryAgg state and executes only downstream dependencies.Verification: three scheduler tests and six maintenance-runtime tests passed. The ERP agent independently reran the real backend process: Planner-selected KLL k=32 and k=128, catalog installation, remote-write ingestion of two series, and warm per-series readout passed without query fallback. This is execution evidence, not a performance comparison.
Stacked on #613 and the merged maintenance fixes. This implements the materialized-input boundary; it does not add arbitrary SummaryAgg update expressions or synchronized multi-source execution. The broader repeated-dashboard process case independently reproduces a preexisting install validator mismatch between pane size and slide; its separate correction belongs to the ERP execution integration.