[
https://issues.apache.org/jira/browse/ARROW-18148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627236#comment-17627236
]
Nicola Crane commented on ARROW-18148:
--------------------------------------
Thanks for taking a look at this in such close detail - interesting to see the
detail there around "stream format" and "file format". I think I'm leaning
towards option 3 seeming like the way to go. I'm not keen on pushing the term
"IPC" on users who are otherwise unaware of it and don't need to be aware of
it, and like the API in option 3.
Perhaps for now, disregard all of this in that PR you have open and those
further docs updates can be made in a follow-up PR once the work to update
these functions is done?
> [R] Rename read_ipc_file to read_arrow_file & highlight arrow over feather
> --------------------------------------------------------------------------
>
> Key: ARROW-18148
> URL: https://issues.apache.org/jira/browse/ARROW-18148
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Documentation, R
> Reporter: Stephanie Hazlitt
> Priority: Minor
> Labels: feather
>
> Following up from [this mailing list
> conversation|https://lists.apache.org/thread/nxncph842h8tyovxp04hrzq4y35lq4xq],
> I am wondering if the R package should rename `read_ipc_file()` /
> write_ipc_file()` to `read_arrow_file()`/ `write_arrow_file()`, or add an
> additional alias for both. It might also be helpful to update the
> documentation so that users read "Write an Arrow file (formerly known as a
> Feather file)" rather than the current Feather-named first approach, assuming
> there is a community decision to coalesce around the name Arrow for the file
> format, and the project is moving on from the name Feather.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
