[
https://issues.apache.org/jira/browse/ARROW-8324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SHIMA Tatsuya reassigned ARROW-8324:
------------------------------------
Assignee: SHIMA Tatsuya
> [R] Add read/write_ipc_file separate from _feather
> --------------------------------------------------
>
> Key: ARROW-8324
> URL: https://issues.apache.org/jira/browse/ARROW-8324
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Neal Richardson
> Assignee: SHIMA Tatsuya
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SeeĀ [https://github.com/apache/arrow/pull/6771#issuecomment-608133760]
> {quote}Let's add read/write_ipc_file also? I'm wary of the "version" option
> in "write_feather" and the Feather version inference capability in
> "read_feather". It's potentially confusing and we may choose to add options
> to write_ipc_file/read_ipc_file that are more developer centric, having to do
> with particulars in the IPC format, that are not relevant or appropriate for
> the Feather APIs.
> IMHO it's best for "Feather format" to remain an abstracted higher-level
> concept with its use of the "IPC file format" as an implementation detail,
> and segregated from the other things.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)