Task Summary
Add a generic controller-side primitive that allows workflow execution to continue from the region containing a specified target operator (JumpToOperatorRegion).
Design constraints:
- The schedule generated by
WorkflowScheduler remains static; the jump primitive does not live in WorkflowScheduler.
- Execution-position state is owned by
WorkflowExecutionCoordinator; a jump rewrites only the coordinator's view of the remaining schedule.
Schedule provides O(1) operator→level-index lookup and a rewriteExecutionFrom data primitive; jump policy stays out of Schedule.
Concretely the change adds:
JumpToOperatorRegionRequest and the JumpToOperatorRegion controller RPC.- A controller handler (
JumpToOperatorRegionHandler) that delegates to the coordinator.
- Coordinator-owned jump support:
replaceSchedule, pullNextRegions, jumpToRegionContainingOperator.
Out of scope: loop-operator logic, region-restart logic, and state materialization. The primitive is generic so those features can build on it.
Priority
P2 – Medium
Task Type
Task Summary
Add a generic controller-side primitive that allows workflow execution to continue from the region containing a specified target operator (
JumpToOperatorRegion).Design constraints:
WorkflowSchedulerremains static; the jump primitive does not live inWorkflowScheduler.WorkflowExecutionCoordinator; a jump rewrites only the coordinator's view of the remaining schedule.Scheduleprovides O(1) operator→level-index lookup and arewriteExecutionFromdata primitive; jump policy stays out ofSchedule.Concretely the change adds:
JumpToOperatorRegionRequestand theJumpToOperatorRegioncontroller RPC.JumpToOperatorRegionHandler) that delegates to the coordinator.replaceSchedule,pullNextRegions,jumpToRegionContainingOperator.Out of scope: loop-operator logic, region-restart logic, and state materialization. The primitive is generic so those features can build on it.
Priority
P2 – Medium
Task Type