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-43021][SQL]
CoalesceBucketsInJoin
not work when using AQE #40688[SPARK-43021][SQL]
CoalesceBucketsInJoin
not work when using AQE #40688Changes from 1 commit
5ae6809
527e6d8
36257ae
2a55aac
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.
shall we put it in
queryStageOptimizerRules
?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.
rules in
queryStageOptimizerRules
are invoked less often which is more efficient. The ruleCoalesceBucketsInJoin
does not change plan partitioning and seems can be put inqueryStageOptimizerRules
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.
In my test , the UT run failed if
CoalesceBucketsInJoin
add inqueryStageOptimizerRules
.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 spend a bit of time understanding why? Then we can write a code comment to explain it and future developers won't try to move this rule to
queryStageOptimizerRules
ever.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.
Yeah , I will provide detailed information and supplement it .
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.
Because
queryStageOptimizerRules
is not applied at the beginning of the init plan. Instead, they are applied in thecreateQueryStages()
method. AndcreateQueryStages()
is bottom-up, which causes the exchange to be eliminated to be wrapped in a layer ofShuffleQueryStage
first, makingCoalesceBucketsInJoin
unrecognizable. And I have added these to the notes at the top. thanks @cloud-fanThere 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.
CoalesceBucketsInJoin
should beforeEnsureRequirements
.