Yicong-Huang opened a new pull request, #6123: URL: https://github.com/apache/texera/pull/6123
### What changes were proposed in this PR? Pure mechanical rename of the two region-scheduling classes, freeing the "Coordinator" name for the upcoming Controller → Coordinator rename (#6122): | Before | After | | --- | --- | | `WorkflowExecutionCoordinator` | `WorkflowExecutionManager` | | `RegionExecutionCoordinator` | `RegionExecutionManager` | | `RegionCoordinatorTestSupport` | `RegionExecutionManagerTestSupport` | The Manager suffix mirrors the `WorkflowExecution` / `RegionExecution` state objects each class owns and drives, following existing precedent (`GlobalReplayManager`, `OutputManager`). Variables (`workflowExecutionCoordinator`, `regionExecutionCoordinators`, `unfinishedRegionCoordinators`, …), comments (including two `RegionExecutionCoordintor` typos), and cross-references in Python comments were updated together. Files moved with `git mv`; no behavior change. ### Any related issues, documentation, discussions? Closes #6121. Prerequisite for #6122. ### How was this PR tested? Refactor with no behavior change — the existing specs were renamed along with the classes and stay green with no assertion edits: ``` sbt "WorkflowExecutionService/testOnly org.apache.texera.amber.engine.architecture.scheduling.WorkflowExecutionManagerSpec org.apache.texera.amber.engine.architecture.scheduling.RegionExecutionManagerSpec" ``` `grep -riE 'ExecutionCoordinator|RegionCoordinator|Coordintor'` over the repo returns no matches after the rename. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 5) -- 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]
