-
Notifications
You must be signed in to change notification settings - Fork 784
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 csv writing of timestamps to show timezone. #849
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #849 +/- ##
==========================================
- Coverage 82.45% 82.28% -0.17%
==========================================
Files 168 168
Lines 48231 48575 +344
==========================================
+ Hits 39767 39971 +204
- Misses 8464 8604 +140 ☔ View full report in Codecov by Sentry. |
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 @novemberkilo !
@alamb @bjchambers I have made changes to the csv writer according to the proposal. While doing so, I have noticed what I think is a bug in the temporal utilities in the kernel. Essentially, variations relating to daylight savings are not recognised at the moment. I have a failing test on a branch here. I came up across this issue during this work as and had to implement https://github.com/novemberkilo/arrow-rs/blob/master/arrow/src/compute/kernels/temporal.rs#L98-L110 to correctly derive the offset for a timezone. I figure I should fix this bug separately -- should I file an issue to describe it and then put up a fix against that? Thanks. |
I think that would make the most sense to me @novemberkilo -- thanks |
Thanks @novemberkilo -- I plan to review this more carefully hopefully today |
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 @novemberkilo this is looking quite nice.
Thanks much for the feedback @alamb -- I have reviewed your comments and made changes accordingly. Something to note, instead of adding |
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.
Looks great -- thank you @novemberkilo
let expected = vec![Some(3), Some(2), Some(1)]; | ||
assert_eq!(actual, expected); | ||
let actual = c3.into_iter().collect::<Vec<_>>(); | ||
let expected = nanoseconds.into_iter().map(|x| Some(x)).collect::<Vec<_>>(); |
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.
👍
I'll plan to merge this tomorrow morning unless anyone else has any comments |
Thanks again @novemberkilo |
* Write timestamps (in csvs) with timezone. * More tests and more verbose naming. * Please linter. * Please clippy. * Cleanup based on review feedback.
* Write timestamps (in csvs) with timezone. * More tests and more verbose naming. * Please linter. * Please clippy. * Cleanup based on review feedback. Co-authored-by: Navin <[email protected]>
Which issue does this PR close?
Closes #778
What changes are included in this PR?
Are there any user-facing changes?
Yes. This changes the behaviour of the csv writer.
// @alamb @bjchambers