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]Improve GpuSequence #4506

Closed
firestarman opened this issue Jan 12, 2022 · 0 comments · Fixed by #4520
Closed

[FEA]Improve GpuSequence #4506

firestarman opened this issue Jan 12, 2022 · 0 comments · Fixed by #4520
Assignees
@firestarman
Labels
task Work required that improves the product but is not user facing
Milestone
Jan 10 - Jan 28

Comments

@firestarman
Copy link
Collaborator

firestarman commented Jan 12, 2022 •
edited
Loading

This is to track the bugs related to GpuSequence

  1. [BUG]GpuSequence blows up when nulls exist in any of the inputs (start, stop, step) #4499
  2. When start < stop but with negative step, CPU blows up, but GPU outputs empty list.
  3. GPU is missing max length check for arrays
@firestarman firestarman added feature request New feature or request ? - Needs Triage Need team to review and classify labels Jan 12, 2022
@firestarman firestarman mentioned this issue Jan 13, 2022
Merged
@sameerz sameerz added task Work required that improves the product but is not user facing and removed feature request New feature or request ? - Needs Triage Need team to review and classify labels Jan 18, 2022
@sameerz sameerz added this to the Jan 10 - Jan 28 milestone Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@firestarman firestarman

Labels
task Work required that improves the product but is not user facing
Projects
None yet
Milestone
Jan 10 - Jan 28
Development

Successfully merging a pull request may close this issue.

GpuSequence refactor[databricks] firestarman/spark-rapids
2 participants
@sameerz @firestarman