-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-48762][SQL] Introduce clusterBy DataFrameWriter API for Python #47452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
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
Contributor
Author
|
This PR depends on #47451 |
d5ad45e to
d223870
Compare
d223870 to
974ccfd
Compare
Contributor
Author
|
Hi @cloud-fan , this PR is ready for review, thanks. |
cloud-fan
approved these changes
Jul 30, 2024
Contributor
|
cc @HyukjinKwon as well |
HyukjinKwon
approved these changes
Jul 30, 2024
Member
|
Merged to master. |
lwz9103
pushed a commit
to Kyligence/spark
that referenced
this pull request
Mar 27, 2025
Introduce clusterBy DataFrameWriter API for Python. Also fix the issue that `listColumns` doesn't support `V1Table`. Introduce more ways for users to interact with clustered tables. Yes, it introduces a new PySpark DataFrame API to specify clustering columns during write operations. New unit tests. No. Closes apache#47452 from zedtang/clusterby-python-api. Authored-by: Jiaheng Tang <jiaheng.tang@databricks.com> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
lwz9103
pushed a commit
to Kyligence/spark
that referenced
this pull request
Apr 22, 2025
Introduce clusterBy DataFrameWriter API for Python. Also fix the issue that `listColumns` doesn't support `V1Table`. Introduce more ways for users to interact with clustered tables. Yes, it introduces a new PySpark DataFrame API to specify clustering columns during write operations. New unit tests. No. Closes apache#47452 from zedtang/clusterby-python-api. Authored-by: Jiaheng Tang <jiaheng.tang@databricks.com> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
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?
Introduce clusterBy DataFrameWriter API for Python.
Also fix the issue that
listColumnsdoesn't supportV1Table.Why are the changes needed?
Introduce more ways for users to interact with clustered tables.
Does this PR introduce any user-facing change?
Yes, it introduces a new PySpark DataFrame API to specify clustering columns during write operations.
How was this patch tested?
New unit tests.
Was this patch authored or co-authored using generative AI tooling?
No.