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.
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
[SPARK-50525][SQL] Define InsertMapSortInRepartitionExpressions Optimizer Rule #49144
[SPARK-50525][SQL] Define InsertMapSortInRepartitionExpressions Optimizer Rule #49144
Changes from all commits
ba29710
2d76099
d7efa2b
75e323b
20c76e4
4b7ec14
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we combine these two rules so that we only need to traverse the plan once?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
initially i wanted to do the same, but logic for
InsertMapSortInGroupingExpressions
andInsertMapSortInRepartitionExpressions
is quite different: Grouping produces a new output after applying the changes, while Repartition only updates existingRepartitionByExpression
by replacingpartitionExpressions
.Also, there is a dependency between
InsertMapSortInGroupingExpressions
andPullOutGroupingExpressions
, as mentioned in this comment.For those reasons i decided to split them into separate Rules. But if you think performance saving from reduced traverse will be significant, we can combine those.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's fine to use
transformUpWithNewOutput
for both. If we hitRepartitionByExpression
, we returnNil
as the new output.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this will make things more complex, while there is no need to return new output for
RepartitionByExpression
. Also, to prevent traverse on every plan we have added two conditions inInsertMapSortInRepartitionExpressions
:_.containsPattern(REPARTITION_OPERATION)
ascond
totransformUpWithPruning
.if rep.partitionExpressions.exists(mapTypeExistsRecursively)
in case matching.So i would keep these two independent from each other.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This newly added test case fails at NON-ANSI mode at the test case,
"decimal(10, 2)"
.