Yicong-Huang commented on PR #4444: URL: https://github.com/apache/texera/pull/4444#issuecomment-4321739809
> > I think we should let the coordinator jump back to a stage, rather than "schedule" or "scheduler". > > Updated based on the review. > > I refactored the implementation so that: > > * `Schedule` remains static/immutable > * `WorkflowScheduler` only produces and holds the generated schedule > * `WorkflowExecutionCoordinator` owns the current execution position and handles `jumpToOperator(...)` Thanks a lot! Let's keep plan/schedule those data classes immutable. I can later add tests to guard this property. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
