You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Lefty Leverenz (JIRA)" <ji...@apache.org> on 2016/11/01 05:57:59 UTC

[jira] [Commented] (HIVE-15056) Support index shifting for struct fields

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

Lefty Leverenz commented on HIVE-15056:
---------------------------------------

[~csun], this issue has fix version 2.1.1 but the commit went to master (2.2.0), not branch-2.1.  Will it also be committed to branch-2.1?

> Support index shifting for struct fields
> ----------------------------------------
>
>                 Key: HIVE-15056
>                 URL: https://issues.apache.org/jira/browse/HIVE-15056
>             Project: Hive
>          Issue Type: Sub-task
>          Components: File Formats, Physical Optimizer, Serializers/Deserializers
>            Reporter: Chao Sun
>            Assignee: Chao Sun
>             Fix For: 2.1.1
>
>         Attachments: HIVE-15056.1.patch, HIVE-15056.2.patch
>
>
> In HIVE-13873, the following case doesn't work:
> {code}
> select s.c from tbl
> {code}
> where {{tbl}} is of schema:
> {code}
> a                   	int
> s                   	struct<b:int,c:string>
> {code}
> This is because currently we generate a "pruned" schema (in terms of {{GroupType}}) for Parquet reader to scan the data. However, on the Hive side the object inspector still uses the original schema. In particular, in this case for {{s.c}} the data returned by Parquet reader is in index 0, but the object inspector tries to read it in index 1. Therefore, in correct result will be returned.



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