aglinxinyuan commented on PR #4444: URL: https://github.com/apache/texera/pull/4444#issuecomment-4323341199
Updated. I restored the iterator-style boundary for `WorkflowExecutionCoordinator`. It no longer reads `Schedule` directly. Instead, it only depends on: - a `getNextRegions: () => Set[Region]` provider - a callback for jumping to the region containing a target operator So the coordinator remains an iterator consumer, and the schedule/cursor logic stays outside of it. -- 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]
