[
https://issues.apache.org/jira/browse/ARROW-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neal Richardson resolved ARROW-5501.
------------------------------------
Resolution: Fixed
Issue resolved by pull request 6771
[https://github.com/apache/arrow/pull/6771]
> [R] Reorganize read/write file/stream functions
> -----------------------------------------------
>
> Key: ARROW-5501
> URL: https://issues.apache.org/jira/browse/ARROW-5501
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Neal Richardson
> Assignee: Neal Richardson
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.17.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> read_feather and write_feather exist, and there is also write_arrow. But no
> read_arrow.
> Some questions (which go beyond just R): There's talk of a "feather 2.0",
> i.e. "just" serializing the IPC format (which IIUC is what write_arrow does).
> Are we going to continue to call the file format "Feather", and possibly
> continue supporting the "feather 1.0" format as a subset/special case? Or
> will "feather" mean this limited format and "arrow" be the name of the
> full-featured file?
> In terms of this issue, should write_arrow be folded into write_feather and
> there be an argument for indicating which version to write? Or should the
> distinction be maintained, and we need to add a read_arrow() function?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
