Conversation
This was referenced Sep 23, 2026
…al-stack-771 # Conflicts: # control_plane/src/physical/compiler.rs # data_plane/tests/e2e_controller_plans_and_backend_serves.rs
This was referenced Sep 26, 2026
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.
Dependency stack: main → #768 → #737 → #749 → #771 → #774 → #763 → #765 → #761 → #728 → #742 → #759
Before this PR
Typed summary support needed by the ten-query workload was mixed with the Level 1 acceptance tests.
After this PR
Keep production summary-plan support in this layer and the per-query plan checks in #728. #774 consumes the Planner-owned physical library; #763 and #765 integrate precompute and query execution. This PR does not introduce another physical-operator implementation.
Bound-query SDS implementation and the new Planner pin are introduced in #774 and inherited downstream. The completed stack separates semantic definitions from deployed output identities and validates installation, reads and recovery. Ad-hoc SDS discovery remains future work.
Validation
The combined stack passes the Level 1 suite and all seven Level 2 differential suites. These are downstream integration results, not a claim of a separate full test run on this scope-only branch. Actual #728 plans are exported for human review; Level 3 performance is reported separately in #759.