[
https://issues.apache.org/jira/browse/HIVE-15056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607286#comment-15607286
]
ASF GitHub Bot commented on HIVE-15056:
---------------------------------------
GitHub user sunchao opened a pull request:
https://github.com/apache/hive/pull/108
HIVE-15056: Support index shifting for struct fields
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sunchao/hive column-pruning
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/108.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #108
----
commit 1532f9e36551eb695fe832d97f31b4dce3eda15b
Author: Chao Sun <[email protected]>
Date: 2016-10-25T21:12:02Z
HIVE-15056: Support index shifting for struct fields
----
> 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
>
> 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)
