hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-6052) metastore JDO filter pushdown for integers may produce unexpected results with non-normalized integer columns
Date Fri, 20 Dec 2013 01:10:07 GMT

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

Ashutosh Chauhan commented on HIVE-6052:
----------------------------------------

Also add same info on config variable in release notes field of jira as Xuefu suggested.

> metastore JDO filter pushdown for integers may produce unexpected results with non-normalized
integer columns
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-6052
>                 URL: https://issues.apache.org/jira/browse/HIVE-6052
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.12.0, 0.13.0
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>             Fix For: 0.13.0
>
>         Attachments: HIVE-6052.01.patch, HIVE-6052.02.patch, HIVE-6052.patch
>
>
> If integer partition columns have values stores in non-canonical form, for example with
leading zeroes, the integer filter doesn't work. That is because JDO pushdown uses substrings
to compare for equality, and SQL pushdown is intentionally crippled to do the same to produce
same results.
> Probably, since both SQL pushdown and integers pushdown are just perf optimizations,
we can remove it for JDO (or make configurable and disable by default), and uncripple SQL.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message