[SPARK-54073] Improve ConfOptionDocGenerator to generate a sorted doc by config key
#407
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
…onfig doc by key
Member
Author
|
cc @jiangzho , @viirya , @peter-toth |
dongjoon-hyun
changed the title
ConfOptionDocGenerator to generate a sorted config doc by keyConfOptionDocGenerator to generate a sorted doc by config key
peter-toth
approved these changes
Oct 29, 2025
Member
Author
|
Thank you, @peter-toth . Merged to main. |
Member
Author
|
Thank you, @viirya ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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 improve
ConfOptionDocGeneratorto generate a sorted config doc by key.Why are the changes needed?
To maintain
docs/config_properties.mdin the alphabetic order always.Does this PR introduce any user-facing change?
No
Spark Operatorbehavior change.How was this patch tested?
Pass the CIs and check the generated doc manually.
Was this patch authored or co-authored using generative AI tooling?
No.