Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Sat, 18 Oct 2014 18:42:34 +0000 (UTC)
From: "Alan Gates (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12749056.1413657586000.291561.1413657754017@Atlassian.JIRA>
In-Reply-To: <JIRA.12749056.1413657586000@Atlassian.JIRA>
References: <JIRA.12749056.1413657586000@Atlassian.JIRA>
 <JIRA.12749056.1413657586890@arcas>
Subject: [jira] [Commented] (HIVE-8515) Column projection not being pushed
 to ORC delta files
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alan Gates commented on HIVE-8515:
----------------------------------

The issue is in OrcInputFormat.getReader:
{code}
    if (split.hasBase()) {
      bucket = AcidUtils.parseBaseBucketFilename(split.getPath(), conf)
          .getBucket();
      reader = OrcFile.createReader(path, OrcFile.readerOptions(conf));
      final List<OrcProto.Type> types = reader.getTypes();
      setIncludedColumns(readOptions, types, conf, split.isOriginal());
      setSearchArgument(readOptions, types, conf, split.isOriginal());
    } else {
      bucket = (int) split.getStart();
      reader = null;
    }
}
{code}

setIncludeColumns is called if there is a base, but not if there isn't.

> Column projection not being pushed to ORC delta files
> -----------------------------------------------------
>
>                 Key: HIVE-8515
>                 URL: https://issues.apache.org/jira/browse/HIVE-8515
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.14.0
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>
> Currently when only some columns are projected, that projection is pushed to the base file but not to delta files.  This does not cause incorrect results (the columns are projected out later in the query execution), but it is less efficient then it could be.


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