[jira] [Comment Edited] (PARQUET-113) Clarify parquet-format specification for LIST and MAP structures.

["Philippe Girolami (JIRA)" <ji...@apache.org>]

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

Philippe Girolami edited comment on PARQUET-113 at 2/2/15 9:27 AM:
-------------------------------------------------------------------

[~rdblue] We've been hit with these issues using parquet-proto. We'd like to know whether changing our "raw" protobuf data model to fit the 2 or 3 level structure for arrays is a good idea : we're afraid once PARQUET-113 gets implemented in parquet-protobuf then we will end up with a 4 or 6 level structure. Any thoughts on this ?


was (Author: pgirolami):
[~rdblue] We've been hit with these issues using parquet-ptoo. We'd like to know whether changing our "raw" protobuf data model to fit the 2 or 3 level structure for arrays is a good idea : we're afraid once PARQUET-113 gets implemented in parquet-protobuf then we will end up with a 4 or 6 level structure. Any thoughts on this ?

> Clarify parquet-format specification for LIST and MAP structures.
> -----------------------------------------------------------------
>
>                 Key: PARQUET-113
>                 URL: https://issues.apache.org/jira/browse/PARQUET-113
>             Project: Parquet
>          Issue Type: Bug
>          Components: parquet-format, parquet-mr
>            Reporter: Ryan Blue
>            Assignee: Ryan Blue
>
> There are incompatibilities in the way that some parquet object models translate nested structures annotated by LIST and MAP / MAP_KEY_VALUE. We need to define clearly what the structures should look like and how to interpret existing structures, including what must be supported to read current parquet-avro, parquet-thrift, etc. files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)