You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Liya Fan (JIRA)" <ji...@apache.org> on 2019/07/15 01:54:00 UTC

[jira] [Commented] (ARROW-5929) [Java] Define API for ExtensionVector whose data must be serialized prior to being sent via IPC

    [ https://issues.apache.org/jira/browse/ARROW-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884803#comment-16884803 ] 

Liya Fan commented on ARROW-5929:
---------------------------------

[~wesmckinn], many thanks for opening this issue.

I think this is a useful feature covering many important use cases.

> [Java] Define API for ExtensionVector whose data must be serialized prior to being sent via IPC
> -----------------------------------------------------------------------------------------------
>
>                 Key: ARROW-5929
>                 URL: https://issues.apache.org/jira/browse/ARROW-5929
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Java
>            Reporter: Wes McKinney
>            Assignee: Liya Fan
>            Priority: Major
>
> As being discussed on the mailing list, a possible use case for ExtensionVector involves having the Arrow buffers contain pointer-type values referring to memory outside of the Arrow memory heap. In IPC, such vectors would need to be serialized to a wholly Arrow-resident form, such as a VarBinaryVector. We do not have an API to allow for this, so this JIRA proposes to add new functions that can indicate to the IPC layer that an ExtensionVector requires additional serialization to a native Arrow type (in such case, the extension type metadata would be discarded)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)