[
https://issues.apache.org/jira/browse/ARROW-12223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Pitrou closed ARROW-12223.
----------------------------------
Resolution: Not A Bug
Late answer, but I don't think this is a bug indeed. If you want to transport
data between runtimes, there are two official solutions:
* the Arrow IPC protocol
* the Arrow C data interface (only for in-process data sharing, guaranteed
zero-copy)
> ArrayData buffers are inconsistent accross implementations
> ----------------------------------------------------------
>
> Key: ARROW-12223
> URL: https://issues.apache.org/jira/browse/ARROW-12223
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, JavaScript, Rust
> Reporter: Vincent Trumpff
> Priority: Major
>
> ArrayData implementations seems to share close structure fields accross
> languages, but their usage is not consistent accross implementation.
>
> Example using ListArray's offsets buffer, in C++, Rust and JavaScript
> implementation:
> - C++: offset's buffer is the second buffer (validity bitmap is first
> buffer, and buffers are laid in a type-dependant way)
> https://github.com/apache/arrow/blob/master/cpp/src/arrow/array/array_nested.cc#L189
> - Rust: offset's buffer is the first buffer (validity bitmap is not part of
> the collection, and buffers are laid in a type-dependant way)
> https://github.com/apache/arrow/blob/master/rust/arrow/src/array/array_list.rs#L235
> - JavaScript: offset's buffer is the first buffer (they have fixed position)
> [https://github.com/apache/arrow/blob/8e43f23dcc6a9e630516228f110c48b64d13cec6/js/src/data.ts#L125]
>
> Note that we have the same inconsistency for validity and data buffers.
>
> This is important in my project because I would like to transport buffers
> list accross technologies, and ArrayData seemed the easiest structure to
> transport.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
