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

[BUG] GpuBroadcastNestedLoopJoinExec can fail if there are no columns #323

Closed
revans2 opened this issue Jul 6, 2020 · 0 comments · Fixed by #353
Closed

[BUG] GpuBroadcastNestedLoopJoinExec can fail if there are no columns #323

revans2 opened this issue Jul 6, 2020 · 0 comments · Fixed by #353
Assignees
@revans2
Labels
bug Something isn't working
Milestone
Jul 6 - Jul 17

Comments

@revans2
Copy link
Collaborator

revans2 commented Jul 6, 2020

Describe the bug
Doing a broadcast nested loop join with no conditionals followed by a count can cause there to be no columns, only a row count in the data set. This causes the query to crash.

Steps/Code to reproduce bug
A test is being added for this.
@revans2 revans2 added bug Something isn't working ? - Needs Triage Need team to review and classify labels Jul 6, 2020
@revans2 revans2 self-assigned this Jul 14, 2020
@revans2 revans2 added this to the Jul 6 - Jul 17 milestone Jul 14, 2020
@revans2 revans2 mentioned this issue Jul 14, 2020
Merged
@sameerz sameerz removed the ? - Needs Triage Need team to review and classify label Jul 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@revans2 revans2

Labels
bug Something isn't working
Projects
None yet
Milestone
Jul 6 - Jul 17
Development

Successfully merging a pull request may close this issue.

Fix broadcast nested loop join for the no column case revans2/spark-rapids
2 participants
@revans2 @sameerz