wForget commented on PR #41609:
URL: https://github.com/apache/spark/pull/41609#issuecomment-1621080029
> I think we should handle it like what shuffle based join did. If it
introduces extra shuffle then it should follow the behavior of force optimize
skew join.
Thanks @ulysses-you . I have optimized BroadcastHashJoin like what shuffle
based join did and removed the judgment of localShuffleReader to cover the case
in #40312.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
