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

Panchen Xue updated ARROW-1860:
-------------------------------
    Description: 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  (was: {color:red}colored 
text{color}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)

> [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: Panchen Xue
>             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
(v6.4.14#64029)

Reply via email to