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

[FEA] Write tests for AQE skewed join optimization #515

Closed
andygrove opened this issue Aug 5, 2020 · 0 comments · Fixed by #536
Closed

[FEA] Write tests for AQE skewed join optimization #515

andygrove opened this issue Aug 5, 2020 · 0 comments · Fixed by #536
Assignees
Labels
feature request New feature or request P1 Nice to have for release test Only impacts tests

Comments

@andygrove
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Once the AQE PR is merged, we should in theory have better performance with skewed joins, but we currently have no tests to confirm this.

Describe the solution you'd like
I would like unit and/or integration tests that confirm that we handle skewed joins correctly when AQE is enabled.

Describe alternatives you've considered
None.

Additional context
None.

@andygrove andygrove added feature request New feature or request ? - Needs Triage Need team to review and classify test Only impacts tests labels Aug 5, 2020
@andygrove andygrove added this to the Aug 3 - Aug 14 milestone Aug 5, 2020
@andygrove andygrove self-assigned this Aug 5, 2020
@sameerz sameerz added P1 Nice to have for release and removed ? - Needs Triage Need team to review and classify labels Aug 11, 2020
tgravescs pushed a commit to tgravescs/spark-rapids that referenced this issue Nov 30, 2023
Signed-off-by: spark-rapids automation <[email protected]>

Signed-off-by: spark-rapids automation <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request P1 Nice to have for release test Only impacts tests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants