mayurdb opened a new pull request #29097:
URL: https://github.com/apache/spark/pull/29097


   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://spark.apache.org/contributing.html
     2. Ensure you have added or run the appropriate tests for your PR: 
https://spark.apache.org/developer-tools.html
     3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP][SPARK-XXXX] Your PR title ...'.
     4. Be sure to keep the PR description updated to reflect all changes.
     5. Please write your PR title to summarize what this PR proposes.
     6. If possible, provide a concise example to reproduce the issue for a 
faster review.
     7. If you want to add a new configuration, please read the guideline first 
for naming configurations in
        
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
   -->
   
   ### What changes were proposed in this pull request?
   To change SortMergeJoin orientation at runtime using adaptive query execution
   
   
   ### Why are the changes needed?
   For SortMerge join of type EquiJoin, the left and right side of the joins 
are decided on the basis of the user order. In SMJ, the left side of the join 
is streamed and the right side is buffered (matching values). Because of this, 
B SMJ A would perform better than A SMJ B if, sizeOf(B) > sizeOf(A)
   
   With adaptive query execution, once both ShuffleQueryStages corresponding to 
the join have completed and if none of them have sizes lesser than the 
broadcast threshold (the join will not be converted to BroadcastHashJoin), join 
orientation can be changed at run time.
   
   
   ### Does this PR introduce _any_ user-facing change?
   No
   -->
   
   
   ### How was this patch tested?
   - Added unit tests
   - Ran AdaptiveQueryExecSuite
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to