[MINOR][DOCS] Fix site.SPARK_VERSION pattern in RDD Programming Guide #47985
+1
−1
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
HyukjinKwon
approved these changes
Sep 4, 2024
Member
|
Merged to master and branch-3.5 |
HyukjinKwon
pushed a commit
that referenced
this pull request
Sep 4, 2024
Fix site.SPARK_VERSION pattern in RDD Programming Guide. I found this when I was developing #47968 doc fix no doc build no Closes #47985 from yaooqinn/version. Authored-by: Kent Yao <[email protected]> Signed-off-by: Hyukjin Kwon <[email protected]> (cherry picked from commit 90a236e) Signed-off-by: Hyukjin Kwon <[email protected]>
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?
Fix site.SPARK_VERSION pattern in RDD Programming Guide. I found this when I was developing #47968
Why are the changes needed?
doc fix
Does this PR introduce any user-facing change?
no
How was this patch tested?
doc build
Was this patch authored or co-authored using generative AI tooling?
no