[SPARK-53932] Add FAIR schedule examples with Spark (Connect|Thrift) servers
#393
Conversation
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
dongjoon-hyun
changed the title
FAIR schedule examples with Spark (Connect|Thrift) ServersFAIR schedule examples with Spark (Connect|Thrift) servers
Member
Author
|
cc @viirya , @peter-toth , @jiangzho |
viirya
approved these changes
Oct 16, 2025
Member
Author
|
Thank you, @viirya . Merged to main. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 pull request?
This PR aims to add
FAIRschedule examples bySpark 4.1.0-preview2-basedSpark Connect Server(4.1.0-preview2).Spark 4.1.0-preview2-basedSpark Thrift ServerWhy are the changes needed?
To show
FAIRschedule examples which is beneficial in the multi-tenant or concurrent job execution environments.Does this PR introduce any user-facing change?
No behavior change because these are examples.
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.