-
Notifications
You must be signed in to change notification settings - Fork 4k
ARROW-16653: [R] All formats are supported with the lubridate parse_date_time binding
#13506
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
Conversation
9dde78a to
7cb9c69
Compare
paleolimbot
left a comment
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.
Just tiny things...looks great!
|
I think the scope of the Jira is to also test/ check/ make sure all formats are supported with |
Could you add a test/ tests for |
|
LGTM once we have a test with the additional formats we now support & the CI passes. Thanks for your work on lubridate, @rok! 🙏🏻 |
paleolimbot
left a comment
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.
|
Once we remove the guardrails, it would be good to test |
|
@dragosmg Can you create a follow-up ticket for that? |
|
I can, but @rok might be close to a unit test for those additional formats. If he is, I'd rather we have the tests in this PR as they go together. |
|
to clarify, that test would be nice to have, but it doesn't mean that without it the features aren't tested. ultimately, |
👍 |
9257a41 to
ee856ba
Compare
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 your work. I have some minor comments, and a larger concern. I am not convinced the build_formats() now works correctly:
# all the formatting characters should be supported
build_formats("wIpz")
#> Error: "wIpz" `orders` not supported in Arrow
r/R/dplyr-datetime-helpers.R
Outdated
| supported_passed_orders <- intersect(orders, supported_orders) | ||
| formats_list <- map(orders, build_format_from_order) | ||
| formats_length <- map(map(formats_list, nchar), max) | ||
| invalid_orders <- formats_length < 6 |
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 think adding some comments here would help for our future selves. For example, on why you think 6 is a good threshold.
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.
It seems unlikely that < 6 characters is the only threshold for an invalid order?
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'm not exactly sure how to check if an order is valid as it really comes down to strptime implementation used. I'm switching to detecting if no valid formats are present or not and will check what lubridate does.
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.
Lubridate checks against an example of it's input, which is something we can't/won't do.
I'd say erroring on invalid formats and returning NA on unsuccessful parsing would be the thing to do.
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.
Agree. That sounds like a good plan
paleolimbot
left a comment
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 comment everywhere I saw some R code that looked out of place...in general I have little idea what's going on here and I think some comments would help.
r/R/dplyr-datetime-helpers.R
Outdated
| supported_passed_orders <- intersect(orders, supported_orders) | ||
| formats_list <- map(orders, build_format_from_order) | ||
| formats_length <- map(map(formats_list, nchar), max) | ||
| invalid_orders <- formats_length < 6 |
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.
It seems unlikely that < 6 characters is the only threshold for an invalid order?
Co-authored-by: Dewey Dunnington <[email protected]>
b68ad44 to
1cc88c9
Compare
Added this to tests. |
|
Thanks for the reviews @dragosmg @paleolimbot ! |
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. Thanks for sticking with it!
|
@github-actions crossbow submit -g r |
|
Revision: 17b46ab Submitted crossbow builds: ursacomputing/crossbow @ actions-156d8fedd0 |
paleolimbot
left a comment
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.
With these changes it's much more readable...thank you!
|
(The sanitizer error was fixed already and valgrind will likely fail when it completes but that is a separate issue) |
|
Thank you for fast reviews and feedback @dragosmg and @paleolimbot ! |
|
Benchmark runs are scheduled for baseline = f645ffa and contender = 3e87c66. 3e87c66 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
…date_time` binding (#13506) This is to resolve [ARROW-16653](https://issues.apache.org/jira/browse/ARROW-16653). Please note the intent here is to map out currently available formats via a new test. That is to support [ARROW-16395](https://issues.apache.org/jira/browse/ARROW-16395) which will add `ymd_hms() ymd_hm() ymd_h() dmy_hms() dmy_hm() dmy_h() mdy_hms() mdy_hm() mdy_h() ydm_hms() ydm_hm() ydm_h()`. Currently most [lubridate supported flags](https://lubridate.tidyverse.org/reference/parse_date_time.html#details) are available and this adds a test. Remaining are `%q` and `%Op` that we don't need to resolve [ARROW-16395](https://issues.apache.org/jira/browse/ARROW-16395). We could open a ticket for adding support for the two remaining flags to C++ `strptime` or wait for users to request them. Lead-authored-by: Rok <[email protected]> Co-authored-by: Rok Mihevc <[email protected]> Signed-off-by: Dewey Dunnington <[email protected]>
Changes introduced by [ARROW-16653](#13506) were not written up by NEWS.md. Lead-authored-by: Rok <[email protected]> Co-authored-by: Dewey Dunnington <[email protected]> Co-authored-by: Rok Mihevc <[email protected]> Signed-off-by: Dewey Dunnington <[email protected]>
…Hub issue numbers (#34260) Rewrite the Jira issue numbers to the GitHub issue numbers, so that the GitHub issue numbers are automatically linked to the issues by pkgdown's auto-linking feature. Issue numbers have been rewritten based on the following correspondence. Also, the pkgdown settings have been changed and updated to link to GitHub. I generated the Changelog page using the `pkgdown::build_news()` function and verified that the links work correctly. --- ARROW-6338 #5198 ARROW-6364 #5201 ARROW-6323 #5169 ARROW-6278 #5141 ARROW-6360 #5329 ARROW-6533 #5450 ARROW-6348 #5223 ARROW-6337 #5399 ARROW-10850 #9128 ARROW-10624 #9092 ARROW-10386 #8549 ARROW-6994 #23308 ARROW-12774 #10320 ARROW-12670 #10287 ARROW-16828 #13484 ARROW-14989 #13482 ARROW-16977 #13514 ARROW-13404 #10999 ARROW-16887 #13601 ARROW-15906 #13206 ARROW-15280 #13171 ARROW-16144 #13183 ARROW-16511 #13105 ARROW-16085 #13088 ARROW-16715 #13555 ARROW-16268 #13550 ARROW-16700 #13518 ARROW-16807 #13583 ARROW-16871 #13517 ARROW-16415 #13190 ARROW-14821 #12154 ARROW-16439 #13174 ARROW-16394 #13118 ARROW-16516 #13163 ARROW-16395 #13627 ARROW-14848 #12589 ARROW-16407 #13196 ARROW-16653 #13506 ARROW-14575 #13160 ARROW-15271 #13170 ARROW-16703 #13650 ARROW-16444 #13397 ARROW-15016 #13541 ARROW-16776 #13563 ARROW-15622 #13090 ARROW-18131 #14484 ARROW-18305 #14581 ARROW-18285 #14615 * Closes: #33631 Authored-by: SHIMA Tatsuya <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
This is to resolve ARROW-16653.
Please note the intent here is to map out currently available formats via a new test. That is to support ARROW-16395 which will add
ymd_hms() ymd_hm() ymd_h() dmy_hms() dmy_hm() dmy_h() mdy_hms() mdy_hm() mdy_h() ydm_hms() ydm_hm() ydm_h().Currently most lubridate supported flags are available and this adds a test. Remaining are
%qand%Opthat we don't need to resolve ARROW-16395. We could open a ticket for adding support for the two remaining flags to C++strptimeor wait for users to request them.