Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 10 Oct 2016 14:43:21 +0000 (UTC)
From: "Ferdinand Xu (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12973300.1464325108000.782865.1476110601530@Atlassian.JIRA>
In-Reply-To: <JIRA.12973300.1464325108000@Atlassian.JIRA>
References: <JIRA.12973300.1464325108000@Atlassian.JIRA> <JIRA.12973300.1464325108085@arcas>
Subject: [jira] [Updated] (HIVE-13873) Column pruning for nested fields
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 10 Oct 2016 14:43:23 -0000


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

Ferdinand Xu updated HIVE-13873:
--------------------------------
    Attachment: HIVE-13873.1.patch

> Column pruning for nested fields
> --------------------------------
>
>                 Key: HIVE-13873
>                 URL: https://issues.apache.org/jira/browse/HIVE-13873
>             Project: Hive
>          Issue Type: New Feature
>          Components: Logical Optimizer
>            Reporter: Xuefu Zhang
>            Assignee: Ferdinand Xu
>         Attachments: HIVE-13873.1.patch, HIVE-13873.patch, HIVE-13873.wip.patch
>
>
> Some columnar file formats such as Parquet store fields in struct type also column by column using encoding described in Google Dramel pager. It's very common in big data where data are stored in structs while queries only needs a subset of the the fields in the structs. However, presently Hive still needs to read the whole struct regardless whether all fields are selected. Therefore, pruning unwanted sub-fields in struct or nested fields at file reading time would be a big performance boost for such scenarios.


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