-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Investigate and propose parallel sort-merge join #14441
Comments
/pick-up |
It is not a pickable issue! MoreTip : If you want this issue to be picked, you need to add a Warning: None |
@qw4990 can you add a |
This issue does not belong to any SIG. MoreTip : Currently, we only support sig labels starting with Warning: None |
/pick-up |
You do not have a team yet, and the current challenge program only supports team participation. |
/pickup |
Description
In this PR(#14238), we introduce the shuffle executor.
We may use this shuffle executor to implement the parallel sort-merge join by nesting some sort and merge-join executors into a shuffle executor:
Compared with the hash-join we implement now, whose building phase is not parallel, it may utilize more CPU resources to get better performance.
shuffle
to let it support multipledatasources
and pass all existed testsmerge_join
shuffle + merge_join
shuffle + merge_join
Score
6600
Mentor
@qw4990 (Slack ID: Zhang Yuanjia)
Recommend Skills
The text was updated successfully, but these errors were encountered: