[SPARK-49128][CORE] Support custom History Server UI title #47639
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
Member
Author
|
Could you review this PR, @viirya ? |
viirya
approved these changes
Aug 6, 2024
Member
Author
|
Thank you, @viirya ! |
yaooqinn
approved these changes
Aug 7, 2024
HyukjinKwon
approved these changes
Aug 7, 2024
Member
|
Merged to master. |
Member
Author
|
Thank you, @yaooqinn and @HyukjinKwon ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 support custom History Server UI title via a new configuration,
spark.history.ui.title.Why are the changes needed?
Like Spark Master UI, it's helpful to provide an easily distinguishable information when there are multiple Spark history server.
MasterPageto support custom title #47491Does this PR introduce any user-facing change?
No, this is a new feature.
How was this patch tested?
Pass the CIs with newly added test case.
Was this patch authored or co-authored using generative AI tooling?
No.