[SPARK-45965][DOCS][FOLLOW-UP] Document DSv2 partitioning expressions moved to functions.partitioning #43887
Conversation
This file contains 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
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 is a followup of #43858 that documents the newly moved functions:
org.apache.spark.sql.functions.partitioning.*becomes Scala-specific because they can't be used in Java side.org.apache.spark.sql.functions.*remain as Java-specific.pyspark.sql.functions.partitioning.*, and remove deprecatedpyspark.sql.functions.*.Why are the changes needed?
For users to use the moved functions.
Does this PR introduce any user-facing change?
The main change has not been released out yet, so no. It adds the newly moved functions into the docs.
How was this patch tested?
Manually tested by building docs (Python).
Was this patch authored or co-authored using generative AI tooling?
No.