[SPARK-50496][SQL]Change rebalance partitioning to SinglePartition if partition number is 1 #49085
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
guixiaowen
changed the title
guixiaowen
changed the title
added 3 commits
December 6, 2024 14:19
… partition number is 1
… partition number is 1
… partition number is 1
Contributor
Author
|
@dongjoon-hyun Could you review this renaming PR |
Contributor
Author
|
@zhengruifeng Could you review this PR |
|
We're closing this PR because it hasn't been updated in a while. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
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.
Change partitioning to SinglePartition.
What changes were proposed in this pull request?
For node RebalanceByExpression, if partition number is 1 we can use SinglePartition instead of other Partitioning.
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
Add test