-
Notifications
You must be signed in to change notification settings - Fork 915
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 index handling in parquet reader and writer #6771
Conversation
Please update the changelog in order to start CI tests. View the gpuCI docs here. |
Codecov Report
@@ Coverage Diff @@
## branch-0.17 #6771 +/- ##
===============================================
+ Coverage 81.92% 81.93% +0.01%
===============================================
Files 96 96
Lines 16167 16166 -1
===============================================
+ Hits 13245 13246 +1
+ Misses 2922 2920 -2
Continue to review full report at Codecov.
|
@property | ||
def step(self): | ||
""" | ||
The value of the step parameter. | ||
""" | ||
return self._step | ||
|
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.
Thanks for catching the missing step
property!
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.
One minor change, otherwise LGTM
Fixes: #6337 , #6740
The actual issue was that cudf was failing to read/write a dataframe for any case other than a RangeIndex/named Multi-Index(all-levels), so this PR revamps index writing and retrieval logic to and from parquet metadata.
This PR:
step
attribute toRangeIndex
.RangeIndex
withstep
value other than 1 was failing incudf.from_pandas
.