-
Notifications
You must be signed in to change notification settings - Fork 917
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
Fix encode/decode of negative timestamps in ORC reader/writer #11586
Fix encode/decode of negative timestamps in ORC reader/writer #11586
Conversation
…bug-orc-negative-timestamp
…bug-orc-negative-timestamp
…bug-orc-negative-timestamp
…bug-orc-negative-timestamp
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## branch-22.10 #11586 +/- ##
===============================================
Coverage ? 86.42%
===============================================
Files ? 145
Lines ? 23009
Branches ? 0
===============================================
Hits ? 19885
Misses ? 3124
Partials ? 0 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
…bug-orc-negative-timestamp
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 with two non-blocking nits
Co-authored-by: Yunsong Wang <[email protected]>
FYI: I have tested this with Spark and no longer see the issue. Thanks for working on it. |
…bug-orc-negative-timestamp
…/cudf into bug-orc-negative-timestamp
rerun tests |
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.
Test refactoring is 🔥, nice work!
@gpucibot merge |
Description
Fixes #11525
Contains a chain of fixes:
int64_t
) - fixes reading of cuDF encoded negative nanoseconds;int64_t
- follows the specs and fixes reading of negative nanoseconds using non-cuDF readers.Checklist