cloud-fan edited a comment on pull request #29692:
URL: https://github.com/apache/spark/pull/29692#issuecomment-690931387


   If the user manually adds a shuffle (DISTRIBUTE BY) in the query before 
broadcast join, I think we can take care of the skew. Spark query optimizer 
should not add the extra shuffle by itself, as it's likely to cause perf 
regression.
   
   But we need to be careful to break output partitioning by splitting the 
skewed partitions, and cause extra shuffle.


----------------------------------------------------------------
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