Make easier to create custom schedulers and executors #1118
Conversation
This file contains 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
milenkovicm
force-pushed
the
feature_custom_binaries
branch
from
d28ecc0
to
1b1d228
Compare
milenkovicm
changed the title
milenkovicm
force-pushed
the
feature_custom_binaries
branch
6 times, most recently
from
9bd1c4d
to
9a04097
Compare
milenkovicm
force-pushed
the
feature_custom_binaries
branch
from
9a04097
to
dfe8aef
Compare
andygrove
approved these changes
Nov 21, 2024
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?
Closes #1115
Rationale for this change
Users should be able to customize scheduler and executors with custom object stores, memory managers and so on ...
removing responsibility from ballista to provide fit all solution
What changes are included in this PR?
Are there any user-facing changes?
Additional context