You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Antoine Pitrou (Jira)" <ji...@apache.org> on 2019/11/14 13:00:00 UTC

[jira] [Closed] (ARROW-1403) [C++] Add variant of SerializeRecordBatch that accepts an writer-allocator callback

     [ https://issues.apache.org/jira/browse/ARROW-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Antoine Pitrou closed ARROW-1403.
---------------------------------
    Resolution: Abandoned

Closing as outdated.

> [C++] Add variant of SerializeRecordBatch that accepts an writer-allocator callback
> -----------------------------------------------------------------------------------
>
>                 Key: ARROW-1403
>                 URL: https://issues.apache.org/jira/browse/ARROW-1403
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Wes McKinney
>            Priority: Major
>
> When writing to other kinds of interfaces, like GPU, it would be useful to be able to pass a function or closure that can instantiate an instance of {{OutputStream}} (which might write to CPU memory, GPU, etc.) given the computed size of the record batch. Currently we allocate new CPU memory and write to that buffer, but this would eliminate an intermediate copy.
> So something like
> {code}
> typedef std::function<Status(const int64_t, std::unique_ptr<OutputStream>*)> StreamCreator;
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)