[
https://issues.apache.org/jira/browse/PARQUET-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301646#comment-14301646
]
Ryan Blue commented on PARQUET-113:
-----------------------------------
Thanks for taking a look, [~pgirolami]. The plan with parquet-proto is to not
do any translation and to not add MAP or LIST annotations at all. The spec
states that unannotated repeated groups should be converted to required lists
of required items, so you would end up with the exact same structure you work
with in protobuf if you read from parquet-avro or the other object models. If
that's something we should change, please let me know. Otherwise, I think that
addresses your concern that your structure will be inflated, right?
> 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)
