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

Support RangePartitioning with native shuffle #458

Open
Tracked by #858
andygrove opened this issue May 22, 2024 · 3 comments
Open
Tracked by #858

Support RangePartitioning with native shuffle #458

andygrove opened this issue May 22, 2024 · 3 comments
Labels
enhancement New feature or request performance

Comments

@andygrove
Copy link
Member

What is the problem the feature request solves?

We do not currently support RangePartitioning with native shuffle.

Adding this support would allow us to use native shuffle for more queries, including queries where there is a global sort.

Describe the potential solution

No response

Additional context

No response

@andygrove andygrove added enhancement New feature or request performance labels May 22, 2024
@viirya
Copy link
Member

viirya commented May 22, 2024

Since the early development of Comet shuffle, this is one item on to do list. After we finish columnar shuffle which has higher coverage and support main partitioning types, we turn our focus to other more urgent items. Because we want to increase query coverage as much as possible. Currently we can run TPC-H queries mostly native, seems we can go back to look at this as it can give us more performance gain on shuffle (because native shuffle is faster than columnar shuffle).

@viirya
Copy link
Member

viirya commented May 22, 2024

I will work on this after finishing HashJoin build right support.

@viirya viirya self-assigned this May 22, 2024
@andygrove andygrove added this to the 0.4.0 milestone Oct 3, 2024
@andygrove andygrove self-assigned this Oct 3, 2024
@andygrove
Copy link
Member Author

This would help with TPC-H performance, so I plan on taking a look at this issue soon

@andygrove andygrove removed this from the 0.4.0 milestone Oct 25, 2024
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
Projects
None yet
Development

No branches or pull requests

2 participants