[WIP][SPARK-29962][SQL] Avoid changing SMJ to BHJ if one side is non-shuffle and the other side can be broadcast#26600
Closed
wangyum wants to merge 1 commit intoapache:masterfrom
wangyum:SPARK-29962
Closed
[WIP][SPARK-29962][SQL] Avoid changing SMJ to BHJ if one side is non-shuffle and the other side can be broadcast#26600wangyum wants to merge 1 commit intoapache:masterfrom wangyum:SPARK-29962
wangyum wants to merge 1 commit intoapache:masterfrom
wangyum:SPARK-29962
Conversation
…e and the other side can be broadcast
|
Test build #114097 has finished for PR 26600 at commit
|
Member
Author
|
It is hard to say which one is faster. I'm close it. |
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
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?
This PR makes it avoid changing
SMJtoBHJif one side is non-shuffle and the other side can be broadcast becauseSMJif faster thanBHJin this case:Why are the changes needed?
Adaptive query execution should not degrade performance.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test