[
https://issues.apache.org/jira/browse/ARROW-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney resolved ARROW-57.
-------------------------------
Resolution: Fixed
This is done in ARROW-67 -- can can continue to iterate in downstream JIRAs and
discuss on the mailing list.
> Format: Draft data headers IDL for data interchange
> ---------------------------------------------------
>
> Key: ARROW-57
> URL: https://issues.apache.org/jira/browse/ARROW-57
> Project: Apache Arrow
> Issue Type: New Feature
> Components: Format
> Reporter: Wes McKinney
> Assignee: Wes McKinney
>
> From the mailing list discussion, we need to define the structure of data
> headers to describe a "page" of Arrow data. In Apache Parquet these are
> referred to as the data page headers and are separate from the schema
> metadata.
> As part of this JIRA:
> * Choose a technology (it need not be the only one, but it would be good to
> have a reference tool) for representing the data page header in "serialized"
> form (as can be stored in shared memory and interpreted by any system with
> access to that memory). Google's Flatbuffers libraries has been discussed for
> this use case.
> * Draft IDL specification for the data headers
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
