[
https://issues.apache.org/jira/browse/ARROW-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Cook closed ARROW-12292.
----------------------------
Resolution: Not A Problem
Closing this for now because the current behavior seems fine. Can reopen later
if we decide to reconsider this.
> [R] Reconsider behavior of as.<type>.ArrowDatum functions
> ---------------------------------------------------------
>
> Key: ARROW-12292
> URL: https://issues.apache.org/jira/browse/ARROW-12292
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Ian Cook
> Assignee: Ian Cook
> Priority: Major
>
> As discussed at
> [https://github.com/apache/arrow/pull/9942#issuecomment-815315840,] the
> {{as.double()}}, {{as.integer()}}, and {{as.character()}} methods for
> {{ArrowDatum}} return R vectors of the specified R types, whereas in dplyr,
> these same functions perform casts to the analogous Arrow types
> Compare the definitions:
> * {{ArrowDatum}} methods:
> [https://github.com/apache/arrow/blob/ace2bfc160e049b4edc7ffb55081cfb7210d6e43/r/R/arrow-datum.R#L139-L145]
> * dplyr functions:
> [https://github.com/apache/arrow/blob/f2db785c24015b102db9b268c67a6ea73c5d7e93/r/R/dplyr.R#L399-L432]
> Consider whether the {{ArrowDatum}} methods should instead perform casts but
> keep the data in Arrow so that the user would have to also call
> {{as.vector()}} to return the data as an R vector.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
