Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 26 Oct 2016 06:05:58 +0000 (UTC)
From: "Chao Sun (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13015149.1477416201000.86632.1477461958357@Atlassian.JIRA>
In-Reply-To: <JIRA.13015149.1477416201000@Atlassian.JIRA>
References: <JIRA.13015149.1477416201000@Atlassian.JIRA> <JIRA.13015149.1477416201128@arcas>
Subject: [jira] [Updated] (HIVE-15056) Support index shifting for struct
 fields
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 26 Oct 2016 06:06:00 -0000


     [ https://issues.apache.org/jira/browse/HIVE-15056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chao Sun updated HIVE-15056:
----------------------------
    Attachment: HIVE-15056.2.patch

> 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
>         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)