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

EPIC: Implement/investigate other join types #13181

Open
3 tasks
Dandandan opened this issue Oct 30, 2024 · 3 comments
Open
3 tasks

EPIC: Implement/investigate other join types #13181

Dandandan opened this issue Oct 30, 2024 · 3 comments
Labels
enhancement New feature or request performance Make DataFusion faster

Comments

@Dandandan
Copy link
Contributor

Dandandan commented Oct 30, 2024

c### Is your feature request related to a problem or challenge?

From http://btw2017.informatik.uni-stuttgart.de/slidesandpapers/F1-10-37/paper_web.pdf

There is this useful overview of join types used by HyPer:
image

We can investigate the following:

Describe the solution you'd like

Implement these types and use them in the planner to improve performance on TPC-H and TPC-DS queries

Describe alternatives you've considered

No response

Additional context

No response

@comphead
Copy link
Contributor

Thanks @Dandandan Now I understand how exotic join types (RightSemi, RightAnti) are coming into play

@Lordworms
Copy link
Contributor

I would like to try group join

@ngli-me
Copy link
Contributor

ngli-me commented Nov 9, 2024

Hi, do you mind if I try taking single join + making an issue for it? I see a description (pg 5), along with some pseudo code (pg 13), hopefully this seems accurate.
http://btw2017.informatik.uni-stuttgart.de/slidesandpapers/F1-10-37/paper_web.pdf

I think this, along with your in progress code is a reasonable reference for me to start trying from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request performance Make DataFusion faster
Projects
None yet
Development

No branches or pull requests

4 participants