[CELEBORN-2409] Fix outdated Spark version descriptions in docs - #3788
Open
yew1eb wants to merge 1 commit into
Open
[CELEBORN-2409] Fix outdated Spark version descriptions in docs#3788yew1eb wants to merge 1 commit into
yew1eb wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Fix outdated Spark version descriptions in docs:
README.md: add Spark 4.1/4.2 to the supported Spark versions listdocs/README.md,docs/deploy.md: "clients for Spark 2.x and Spark 3.x" -> "clients for Spark 2.x, Spark 3.x and Spark 4.x"docs/developers/sbt.md: update the shaded client publish example from-Pspark-4.0to-Pspark-4.2, aligning withbuild/release/release.shWhy are the changes needed?
Spark 4.1/4.2 support was added in CELEBORN-2239 and CELEBORN-2383, but these doc descriptions were not updated accordingly.
Does this PR resolve a correctness bug?
Does this PR introduce any user-facing change?
How was this patch tested?
Doc-only changes, no code changes.