[
https://issues.apache.org/jira/browse/ARROW-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330782#comment-16330782
]
Wes McKinney commented on ARROW-1860:
-------------------------------------
[~1xuepanchen1] I'm going to take a look at this if you don't mind. There are
some nuances in the IPC writer around handling sliced bitmaps (see
https://github.com/apache/arrow/blob/master/cpp/src/arrow/ipc/writer.cc#L125),
and I want to see if we can improve the write performance in microbenchmarks
while doing this refactoring
> [C++] Add data structure to "stage" a sequence of IPC messages from in-memory
> data
> ----------------------------------------------------------------------------------
>
> Key: ARROW-1860
> URL: https://issues.apache.org/jira/browse/ARROW-1860
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Major
> Fix For: 0.9.0
>
> Attachments: text.html
>
>
> Currently, when you need to pre-allocate space for a record batch or a stream
> (schema + dictionaries + record batches), you must make multiple passes over
> the data structures of interest (and use e.g. {{MockOutputStream}} to compute
> the size of the output buffer). It would be useful to make a single pass to
> "prepare" the IPC payload for both sizing and writing to prevent having to
> make multiple passes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
