chore(amber): remove the unused DeployStrategy family - #7705
Open
aglinxinyuan wants to merge 1 commit into
Open
Conversation
Contributor
Automated Reviewer SuggestionsBased on the
|
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
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.
What changes were proposed in this PR?
Deletes the
deploystrategypackage — theDeployStrategytrait, its three implementations (OneOnEach,RandomDeployment,RoundRobinDeployment) and their shared spec. Pure deletion, no behaviour change: −293 lines.Nothing has called any of them since #1807 (2023-02-02, "[Compiler Refactor 6] Refactor Amber Workflow to use the new PhysicalPlan implementation"). Searching both by symbol name and by package path, the only files that reference the four types are the package's own files and its spec.
Worker placement is now inline.
ExecutorDeployment.createWorkerspicks an address straight offAddressInfo:addressInfo.allAddresses(workerIndex % addressInfo.allAddresses.length)—
RoundRobinDeployment's logic absorbed into the caller.CoordinatorandRegionExecutionManagerreach placement through that path and never touch the trait.Any related issues, documentation, discussions?
Closes #7704
How was this PR tested?
Existing tests only — this PR adds none, since it removes code and the spec that covered it.
Locally, from the repo root with Java 17:
sbt "WorkflowExecutionService/Test/compile"— success (main and test sources).Verification, re-runnable by a reviewer:
Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 5)