-
Notifications
You must be signed in to change notification settings - Fork 871
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
[REVIEW] Fix columns
& index
handling in dataframe constructor
#6838
Conversation
Please update the changelog in order to start CI tests. View the gpuCI docs here. |
Codecov Report
@@ Coverage Diff @@
## branch-0.18 #6838 +/- ##
===============================================
+ Coverage 81.53% 82.00% +0.46%
===============================================
Files 96 96
Lines 15876 16245 +369
===============================================
+ Hits 12945 13321 +376
+ Misses 2931 2924 -7
Continue to review full report at Codecov.
|
columns
& index
handling in dataframe constructorcolumns
& index
handling in dataframe constructor
At a high level it looks like this shares some logic with Can we find a way to reuse code between the two? |
columns
& index
handling in dataframe constructorcolumns
& index
handling in dataframe constructor
columns
& index
handling in dataframe constructorcolumns
& index
handling in dataframe constructor
columns
& index
handling in dataframe constructorcolumns
& index
handling in dataframe constructor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The dask_cudf changes seem fine to me. If the map_partitions
call could happen on a large graph, I would suggest that we find a way to push the set_index
operation into an earlier task. However, this is a single-partition dask_cudf.DataFrame
by design, so graph size will never be an issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Fixes: #6821
This PR fixes issue where
columns
andindex
are currently not being handled correctly in specific scenarios.