Skip to content
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

Closed
4 tasks done
qw4990 opened this issue Jan 10, 2020 · 7 comments · Fixed by #21360
Closed
4 tasks done

Investigate and propose parallel sort-merge join #14441

qw4990 opened this issue Jan 10, 2020 · 7 comments · Fixed by #21360
Assignees
Labels
challenge-program help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/execution SIG execution type/enhancement The issue or PR belongs to an enhancement.

Comments

@qw4990
Copy link
Contributor

qw4990 commented Jan 10, 2020

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:

ShuffleExec
    - MergeJoinExec
        - SortExec
    - MergeJoinExec
        - SortExec
    ...

Compared with the hash-join we implement now, whose building phase is not parallel, it may utilize more CPU resources to get better performance.

  • Modify the original shuffle to let it support multiple datasources and pass all existed tests
  • Introduce a new variable to control concurrency of merge_join
  • Support shuffle + merge_join
  • Add some correct tests and benchmarks about shuffle + merge_join

Score

6600

Mentor

@qw4990 (Slack ID: Zhang Yuanjia)

Recommend Skills

  • Golang
@qw4990 qw4990 added type/enhancement The issue or PR belongs to an enhancement. difficulty/medium help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jan 10, 2020
@hftsin
Copy link

hftsin commented Sep 10, 2020

/pick-up

@ti-challenge-bot
Copy link

It is not a pickable issue!

More

Tip : If you want this issue to be picked, you need to add a challenge-program label to it.

Warning: None

@hftsin
Copy link

hftsin commented Sep 10, 2020

@qw4990 can you add a challenge-program label to this issue?

@ti-challenge-bot
Copy link

This issue does not belong to any SIG.

More

Tip : Currently, we only support sig labels starting with sig/, maybe you should add this type of label.

Warning: None

@huang-b
Copy link
Contributor

huang-b commented Oct 5, 2020

/pick-up

@ti-challenge-bot
Copy link

You do not have a team yet, and the current challenge program only supports team participation.

@huang-b
Copy link
Contributor

huang-b commented Oct 13, 2020

/pickup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
challenge-program help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/execution SIG execution type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants