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 2021/12/16 00:45:00 UTC

[jira] [Assigned] (ARROW-14557) [R] Review functions exported from stringr and make JIRAs for making the Arrow equivalents

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

Nicola Crane reassigned ARROW-14557:
------------------------------------

    Assignee: Nicola Crane

> [R] Review functions exported from stringr and make JIRAs for making the Arrow equivalents 
> -------------------------------------------------------------------------------------------
>
>                 Key: ARROW-14557
>                 URL: https://issues.apache.org/jira/browse/ARROW-14557
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: R
>            Reporter: Nicola Crane
>            Assignee: Nicola Crane
>            Priority: Major
>
> We don't currently have a simple/consistent way to track which exported functions for string parsing functionality we do or do not support.  We should go through all the exported functions in stringr 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.1#820001)