-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-9860][SQL] Join: Determine the join strategy (broadcast join or shuffle join) at runtime #13028
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
Conversation
|
Test build #58239 has finished for PR 13028 at commit
|
|
Test build #58240 has finished for PR 13028 at commit
|
|
Test build #58241 has finished for PR 13028 at commit
|
|
Test build #58376 has finished for PR 13028 at commit
|
|
Test build #58378 has finished for PR 13028 at commit
|
|
Test build #58481 has finished for PR 13028 at commit
|
|
@lianhuiwang could this regress performance for existing queries? Can you please share some benchmarks with us (if any)? |
|
We are closing it due to inactivity. please do reopen if you want to push it forward. Thanks! |
|
It is great for BI scene. Why not continue? |
What changes were proposed in this pull request?
if size of one exchange is less than autoBroadcastJoinThreshold, it transforms sort merge join to broadcast join.
I will support optimization for skew join in another PR.
How was this patch tested?
unit tests