[
https://issues.apache.org/jira/browse/HIVE-8909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217199#comment-14217199
]
Ryan Blue commented on HIVE-8909:
---------------------------------
Yes, HIVE-8359 should go in first. This should also be followed up with a patch
that implements the write rules for PARQUET-113, which is really just renaming
the fields that Hive currently produces. I'm also particularly interested in
thorough testing for this, but I haven't done much Hive testing myself. That's
why this includes unit tests but not HQL tests. If someone could help me out
with that to make sure this doesn't cause regressions, I would be grateful!
> Hive doesn't correctly read Parquet nested types
> ------------------------------------------------
>
> Key: HIVE-8909
> URL: https://issues.apache.org/jira/browse/HIVE-8909
> Project: Hive
> Issue Type: Bug
> Reporter: Ryan Blue
> Assignee: Ryan Blue
> Attachments: HIVE-8909-1.patch
>
>
> Parquet's Avro and Thrift object models don't produce the same parquet type
> representation for lists and maps that Hive does. In the Parquet community,
> we've defined what should be written and backward-compatibility rules for
> existing data written by parquet-avro and parquet-thrift in PARQUET-113. We
> need to implement those rules in the Hive Converter classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
