You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Nicola Crane (Jira)" <ji...@apache.org> on 2022/10/27 19:31:00 UTC

[jira] [Closed] (ARROW-14556) [R] Review functions exported from clock and lubridate and make JIRAs for making the Arrow equivalents

     [ https://issues.apache.org/jira/browse/ARROW-14556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicola Crane closed ARROW-14556.
--------------------------------
    Resolution: Won't Fix

Closing this as we don't want to blindly do this for every single function, and need to take a more judicious approach to work out what to implement

> [R] Review functions exported from clock and lubridate and make JIRAs for making the Arrow equivalents
> ------------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-14556
>                 URL: https://issues.apache.org/jira/browse/ARROW-14556
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: R
>            Reporter: Nicola Crane
>            Priority: Major
>
> We don't currently have a simple/consistent way to track which exported functions for datetime functionality we do or do not support.  We should go through all the exported functions in clock and lubridate which could theoretically be implemented in our NSE functions, and create Jira tickets for implementing them. 
> Even if a function cannot be implemented, we then have something searchable we can look for to see why, or to update if this changes, as well as link to the relevant C++ ticket where appropriate.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)