Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Thu, 12 Nov 2015 18:54:10 +0000 (UTC)
From: "Zelaine Fong (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12912044.1447205150000.52975.1447354450992@Atlassian.JIRA>
In-Reply-To: <JIRA.12912044.1447205150000@Atlassian.JIRA>
References: <JIRA.12912044.1447205150000@Atlassian.JIRA>
 <JIRA.12912044.1447205150676@arcas>
Subject: [jira] [Commented] (DRILL-4070) Metadata Caching : min/max values
 are null for varchar columns in auto partitioned data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Zelaine Fong commented on DRILL-4070:
-------------------------------------

Regarding this point:

"So unfortunately it doesn't look like we could modify parquet to provide a special case for the old Drill files, by looking for our older version string in particular."

Although older Drill generated Parquet files don't have a version string, can't you use the non-presence of the version string as an indicator that the file is from an older release?

> Metadata Caching : min/max values are null for varchar columns in auto partitioned data
> ---------------------------------------------------------------------------------------
>
>                 Key: DRILL-4070
>                 URL: https://issues.apache.org/jira/browse/DRILL-4070
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Metadata
>    Affects Versions: 1.3.0
>            Reporter: Rahul Challapalli
>            Priority: Critical
>         Attachments: cache.txt, fewtypes_varcharpartition.tar.tgz
>
>
> git.commit.id.abbrev=e78e286
> The metadata cache file created contains incorrect values for min/max fields for varchar colums. The data is also partitioned on the varchar column
> {code}
> refresh table metadata fewtypes_varcharpartition;
> {code}
> As a result partition pruning is not happening. This was working after DRILL-3937 has been fixed (d331330efd27dbb8922024c4a18c11e76a00016b)
> I attached the data set and the cache file


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