You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Szehon Ho (JIRA)" <ji...@apache.org> on 2014/04/01 00:07:27 UTC

[jira] [Commented] (HIVE-6783) Incompatible schema for maps between parquet-hive and parquet-pig

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

Szehon Ho commented on HIVE-6783:
---------------------------------

Thanks, that is my only concern to not break existing stored maps, I'm ok if thats the case.  Although I wonder, it would seem pig should be able to read hive's maps if that is the case, because we are using pig's schema now to read?  Or is there some difference there?


> Incompatible schema for maps between parquet-hive and parquet-pig
> -----------------------------------------------------------------
>
>                 Key: HIVE-6783
>                 URL: https://issues.apache.org/jira/browse/HIVE-6783
>             Project: Hive
>          Issue Type: Bug
>          Components: File Formats
>    Affects Versions: 0.13.0
>            Reporter: Tongjie Chen
>             Fix For: 0.13.0
>
>         Attachments: HIVE-6783.1.patch.txt, HIVE-6783.2.patch.txt, HIVE-6783.3.patch.txt, HIVE-6783.4.patch.txt
>
>
> see also in following parquet issue:
> https://github.com/Parquet/parquet-mr/issues/290
> The schema written for maps isn't compatible between hive and pig. This means any files written in one cannot be properly read in the other.
> More specifically,  for the same map column c1, parquet-pig generates schema:
> message pig_schema {
>   optional group c1 (MAP) {
>     repeated group map (MAP_KEY_VALUE) {
>       required binary key (UTF8);
>       optional binary value;
>     }   
>   }
> }
> while parquet-hive generates schema:
> message hive_schema {
>    optional group c1 (MAP_KEY_VALUE) {
>      repeated group map {
>        required binary key;
>        optional binary value;
>    }
>  }
> }



--
This message was sent by Atlassian JIRA
(v6.2#6252)