You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Joris Van den Bossche (Jira)" <ji...@apache.org> on 2022/01/10 12:32:00 UTC

[jira] [Commented] (ARROW-15250) [Python][R] Temporal floor/ceil/round for should accept frequency string

    [ https://issues.apache.org/jira/browse/ARROW-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471954#comment-17471954 ] 

Joris Van den Bossche commented on ARROW-15250:
-----------------------------------------------

I think there was also still some doubt on the PR about whether this is actually needed. The question is also how far we would do (eg lubridate seems to support both ISO8601 durations (https://en.wikipedia.org/wiki/ISO_8601#Durations) as more custom abbreviations). 

> [Python][R] Temporal floor/ceil/round for should accept frequency string
> ------------------------------------------------------------------------
>
>                 Key: ARROW-15250
>                 URL: https://issues.apache.org/jira/browse/ARROW-15250
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Python, R
>            Reporter: Rok Mihevc
>            Priority: Minor
>              Labels: good-first-issue, kernel, timestamp
>
> Follow up to ARROW-14822. More user-friendly rounding period input can be supported, e.g. 1D6H. See [Pandas to_offset|https://github.com/pandas-dev/pandas/blob/a6c1f6cccee6bbccfb29488a94664ed07db024d9/pandas/_libs/tslibs/offsets.pyx#L3575-L3679] and [lubridate's period|https://lubridate.tidyverse.org/reference/period.html].



--
This message was sent by Atlassian Jira
(v8.20.1#820001)