Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
SeeĀ https://github.com/apache/arrow/pull/6771#issuecomment-608133760
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.
Attachments
Issue Links
- relates to
-
ARROW-17092 [Docs] Add note about "Feather" to the IPC file format document
- Resolved
-
ARROW-17072 [R] Rename *_feather functions
- Closed
- links to