[SPARK-39402][SQL] Optimize ReplaceCTERefWithRepartition to support coalesce partitions#36790
Closed
wangyum wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-39402][SQL] Optimize ReplaceCTERefWithRepartition to support coalesce partitions#36790wangyum wants to merge 1 commit intoapache:masterfrom
wangyum wants to merge 1 commit intoapache:masterfrom
Conversation
Member
Author
|
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. |
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
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.
What changes were proposed in this pull request?
Optimize
ReplaceCTERefWithRepartitionto support coalesce partitions. For example:Why are the changes needed?
Reduce the overhead of shuffle as much as possible.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test.