Repository navigation
chore(scheduler): remove the no-op disable-stage-plan-cache feature - #2836
Merged
milenkovicm merged 1 commit intoNov 10, 2026
Merged
milenkovicm merged 1 commit into
milenkovicm merged 1 commit into
Conversation
The scheduler stopped caching encoded stage plans in 55.0.0 (apache#2038) and now encodes each task's plan separately, so nothing reads this feature. Remove it, drop it from the two README feature tables, and note the removal in the 56.0.0 upgrade guide.
github-actions
Bot
added
the
documentation
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.
Which issue does this PR close?
No issue filed; small cleanup.
Rationale for this change
#1266 added the
disable-stage-plan-cachefeature to turn off the scheduler's cache of encoded stage plans. #2038 (released in 55.0.0) removed that cache and now encodes each task's plan separately, but left the feature behind. Nothing reads it, yet both READMEs still document it.What changes are included in this PR?
ballista/scheduler/Cargo.toml.README.mdandballista/scheduler/README.md.Are there any user-facing changes?
Behavior is unchanged. Anyone enabling the feature on their
ballista-schedulerdependency must remove it from theirfeatureslist. This should get theapi-changelabel.