You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rok Mihevc / @rok:
The one benefit from shorthands I see is if you want to do an interval of "1D1s" that's cleaner to write as unit="second", multiple=86401 (==24h*60min*60s + 1s).
I'm happy to mark this as Not A Problem and revisit later if users want it.
Joris Van den Bossche / @jorisvandenbossche:
On the other hand, rounding by "1 day and 1 second" is also quite a rare use case, I think? In most common cases, the potential calculation into a multiple and unit will be quite straightforward.
Rok Mihevc / @rok:
Another benefit of having this is to be able to seamlessly replace lubridate/pandas.
I would prefer not to include this feature, just being completist.
Dewey Dunnington / @paleolimbot:
I don't think this will be an issue from a lubridate completist standpoint, since it's hard to round to a period like the one mentioned here:
lubridate::round_date(Sys.time(), unit="1M1S")
#> Error in parse_period_unit(unit): Cannot't parse heterogenuous or fractional units larger than one minute.
Follow up to ARROW-14822. More user-friendly rounding period input can be supported, e.g. 1D6H. See Pandas to_offset and lubridate's period.
Reporter: Rok Mihevc / @rok
Watchers: Rok Mihevc / @rok
Note: This issue was originally created as ARROW-15250. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: