[
https://issues.apache.org/jira/browse/ARROW-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080059#comment-17080059
]
Wes McKinney commented on ARROW-6783:
-------------------------------------
I removed it from the 1.0.0 milestone. I agree that the C interface is a better
solution for in-memory handoffs.
One meaningful deficiency with the C++ IPC implementation is the 0 frame of
reference (relative to the start of the encapsulated message body). So it's
only usable in the context of encapsulated messages. I'll rewrite the JIRA a
bit to reflect this issue (which is non-urgent, but may be interesting to do
something about someday)
> [C++] Provide API for reconstruction of RecordBatch from Flatbuffer
> containing process memory addresses instead of relative offsets into an IPC
> message
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARROW-6783
> URL: https://issues.apache.org/jira/browse/ARROW-6783
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Wes McKinney
> Priority: Major
>
> A lot of our development has focused on _inter_process communication rather
> than _in_process. We should start by making sure we have disassembly and
> reassembly implemented where the Buffer Flatbuffers values contain process
> memory addresses rather than offsets. This may require a bit of refactoring
> so we can use the same reassembly code path for both use cases
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
