-
Notifications
You must be signed in to change notification settings - Fork 245
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] Allow RangePartitioning to work with structs #1607
Labels
task
Work required that improves the product but is not user facing
Comments
5 tasks
this issue depends on |
Modifying this issue to focus on structs, rather than structs and lists. |
gerashegalov
added a commit
to gerashegalov/spark-rapids
that referenced
this issue
May 26, 2021
Relates to NVIDIA#1607 Signed-off-by: Gera Shegalov <[email protected]>
abellina
pushed a commit
that referenced
this issue
May 27, 2021
* Improve test coverage for sorting structs Relates to #1607 Signed-off-by: Gera Shegalov <[email protected]> * cudf fix
abellina
pushed a commit
to abellina/spark-rapids
that referenced
this issue
May 27, 2021
Relates to NVIDIA#1607 Signed-off-by: Gera Shegalov <[email protected]>
nartal1
pushed a commit
to nartal1/spark-rapids
that referenced
this issue
Jun 9, 2021
* Improve test coverage for sorting structs Relates to NVIDIA#1607 Signed-off-by: Gera Shegalov <[email protected]> * cudf fix
nartal1
pushed a commit
to nartal1/spark-rapids
that referenced
this issue
Jun 9, 2021
* Improve test coverage for sorting structs Relates to NVIDIA#1607 Signed-off-by: Gera Shegalov <[email protected]> * cudf fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Once #1605 is in, we should allow nested types as input and output types to the RangePartitioner.
The text was updated successfully, but these errors were encountered: