aglinxinyuan opened a new issue, #7444:
URL: https://github.com/apache/texera/issues/7444
### Task Summary
`ExpansionGreedyScheduleGenerator` has been unreachable since #3144 and
formally deprecated since #3542. Nothing in the repo references it except its
own spec.
| Symbol | Location | Lines (src + spec) | Status |
| --- | --- | ---: | --- |
| `ExpansionGreedyScheduleGenerator` |
`amber/.../engine/architecture/scheduling/` | 495 + 337 | `@deprecated` since
#3542 (2025-07-09) |
#3144 ("Refactoring of Schedule Generation", 2024-12-14) made
`CostBasedScheduleGenerator` the only generator the engine builds —
`WorkflowScheduler.scala:46` instantiates it directly:
```
WorkflowScheduler -> new CostBasedScheduleGenerator(...) (live)
ExpansionGreedyScheduleGenerator (no caller since
#3144)
```
#3542 then annotated the class with the removal notice it still carries:
> This greedy schedule generator will be removed in the future. Use
`CostBasedScheduleGenerator` instead.
There is no generator-selection switch to keep it reachable: the
`schedule-generator` block in `application.conf` holds only CostBased tuning
parameters (`max-concurrent-regions`, `use-global-search`,
`use-top-down-search`, `search-timeout`), and a case-insensitive search for
`greedy` across `.conf` / `.yml` / `.yaml` / `.json` / `.properties` returns
nothing. The abstract base `ScheduleGenerator` stays —
`CostBasedScheduleGenerator` extends it.
Acting on the deprecation notice is a pure deletion with no behaviour
change: −832 lines.
### Task Type
- [x] Refactor / Cleanup
--
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]
