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.

Sign up for GitHub

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

Jump to bottom

[FEA] Disable split join planning once shuffle matches spark shuffle #939

Closed
revans2 opened this issue Oct 13, 2020 · 1 comment
Closed

[FEA] Disable split join planning once shuffle matches spark shuffle #939

revans2 opened this issue Oct 13, 2020 · 1 comment
Labels
feature request New feature or request P1 Nice to have for release performance A performance related task/issue

Comments

@revans2
Copy link
Collaborator

revans2 commented Oct 13, 2020

Is your feature request related to a problem? Please describe.
Once #938 works we can disable the changes we put in place to work around our shuffle not matching spark's. We may want to do this at the very end because if we get it wrong we have data corruption.
@revans2 revans2 added feature request New feature or request ? - Needs Triage Need team to review and classify labels Oct 13, 2020
@sameerz sameerz added P1 Nice to have for release and removed ? - Needs Triage Need team to review and classify labels Oct 20, 2020
@sameerz sameerz added the performance A performance related task/issue label Jan 14, 2021
@sameerz sameerz changed the title [FEA] Disable split join planning once shuffle matchs spark shuffle [FEA] Disable split join planning once shuffle matches spark shuffle Feb 9, 2021
@jlowe
Copy link
Member

jlowe commented Jan 13, 2022

This should now be done.

@jlowe jlowe closed this as completed Jan 13, 2022
tgravescs pushed a commit to tgravescs/spark-rapids that referenced this issue Nov 30, 2023
@nvauto
Merge pull request NVIDIA#939 from NVIDIA/bot-auto-merge-branch-23.02
d00beed 
[auto-merge] bot-auto-merge-branch-23.02 to branch-23.04 [skip ci] [bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request New feature or request P1 Nice to have for release performance A performance related task/issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jlowe @revans2 @sameerz