Conversation
HyukjinKwon
approved these changes
Aug 13, 2026
uros-b
commented
Aug 13, 2026
uros-b
left a comment
uros-b
left a comment
Member
Author
There was a problem hiding this comment.
Thank you @HyukjinKwon!
uros-b
added a commit
that referenced
this pull request
Aug 13, 2026
…e ML guide ### What changes were proposed in this pull request? Removes the `Highlights in 3.0` section from `docs/ml-guide.md`, and rewrites a sentence that still described DataFrame-based API feature parity as future work in the Spark 2.x releases. ### Why are the changes needed? Both are stale on the current codebase. The guide keeps no equivalent `Highlights` section for 1.x or 2.x, so dropping superseded highlights is the established practice: SPARK-30934 replaced the 2.3 highlights with the 3.0 ones rather than accumulating them. The `Migration Guide` section immediately below already points readers to the archived migration guide, and the 3.0 features remain documented on their own pages, so no user-facing information is lost. Feature parity between the DataFrame-based and RDD-based APIs was reached at Spark 2.3, as `ml-pipeline.md` states, so the future-tense sentence is corrected to past tense. ### Does this PR introduce _any_ user-facing change? No, other than the updated documentation. ### How was this patch tested? Documentation only. No internal doc links point at the removed section's anchor, and the surrounding sections remain well-formed after the deletion. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.8) Closes #57987 from uros-b/doc-mlguide-stale-highlights. Authored-by: Uros Bojanic <221401595+uros-b@users.noreply.github.com> Signed-off-by: Uros Bojanic <221401595+uros-b@users.noreply.github.com> (cherry picked from commit 99b57f9) Signed-off-by: Uros Bojanic <221401595+uros-b@users.noreply.github.com>
uros-b
added a commit
that referenced
this pull request
Aug 13, 2026
…e ML guide ### What changes were proposed in this pull request? Removes the `Highlights in 3.0` section from `docs/ml-guide.md`, and rewrites a sentence that still described DataFrame-based API feature parity as future work in the Spark 2.x releases. ### Why are the changes needed? Both are stale on the current codebase. The guide keeps no equivalent `Highlights` section for 1.x or 2.x, so dropping superseded highlights is the established practice: SPARK-30934 replaced the 2.3 highlights with the 3.0 ones rather than accumulating them. The `Migration Guide` section immediately below already points readers to the archived migration guide, and the 3.0 features remain documented on their own pages, so no user-facing information is lost. Feature parity between the DataFrame-based and RDD-based APIs was reached at Spark 2.3, as `ml-pipeline.md` states, so the future-tense sentence is corrected to past tense. ### Does this PR introduce _any_ user-facing change? No, other than the updated documentation. ### How was this patch tested? Documentation only. No internal doc links point at the removed section's anchor, and the surrounding sections remain well-formed after the deletion. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.8) Closes #57987 from uros-b/doc-mlguide-stale-highlights. Authored-by: Uros Bojanic <221401595+uros-b@users.noreply.github.com> Signed-off-by: Uros Bojanic <221401595+uros-b@users.noreply.github.com> (cherry picked from commit 99b57f9) Signed-off-by: Uros Bojanic <221401595+uros-b@users.noreply.github.com>
Member
Author
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
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?
Removes the
Highlights in 3.0section fromdocs/ml-guide.md, and rewrites a sentence that still described DataFrame-based API feature parity as future work in the Spark 2.x releases.Why are the changes needed?
Both are stale on the current codebase. The guide keeps no equivalent
Highlightssection for 1.x or 2.x, so dropping superseded highlights is the established practice: SPARK-30934 replaced the 2.3 highlights with the 3.0 ones rather than accumulating them. TheMigration Guidesection immediately below already points readers to the archived migration guide, and the 3.0 features remain documented on their own pages, so no user-facing information is lost. Feature parity between the DataFrame-based and RDD-based APIs was reached at Spark 2.3, asml-pipeline.mdstates, so the future-tense sentence is corrected to past tense.Does this PR introduce any user-facing change?
No, other than the updated documentation.
How was this patch tested?
Documentation only. No internal doc links point at the removed section's anchor, and the surrounding sections remain well-formed after the deletion.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.8)