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/11/15 11:15:00 UTC

[jira] [Updated] (ARROW-14441) [R] Add our philosophy to the dev vignette

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

Nicola Crane updated ARROW-14441:
---------------------------------
        Parent: ARROW-13407
    Issue Type: Sub-task  (was: Improvement)

> [R] Add our philosophy to the dev vignette
> ------------------------------------------
>
>                 Key: ARROW-14441
>                 URL: https://issues.apache.org/jira/browse/ARROW-14441
>             Project: Apache Arrow
>          Issue Type: Sub-task
>          Components: R
>            Reporter: Jonathan Keane
>            Assignee: Nicola Crane
>            Priority: Major
>
> This isn't necessarily limited to CSVs, but we should have this philosophy in our developing vignette 
> The general approach we've done with CSV things in the past is:
> (1) support the readr signature to the best extent we can, translating to the arrow parameter names internally;
> (2) allow someone to pass the arrow options (CsvReadOptions etc.) directly, in case they want to do things at a lower level
> (3) where necessary add extra args to the readr signature for features that don't exist in R but do in arrow (e.g. schema)
> This is our general philosophy: present things to the R user in a way that is least surprising to them (most follows R conventions) and also provide access to all of Arrow's features (sometimes that's extra args, sometimes it's the arrow_ prefixed functions in dplyr, sometimes it's just the lower-level R6 objects and methods that more closely follow the C++ interface)



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