[jira] [Commented] (HIVE-6052) metastore JDO filter pushdown for integers may produce unexpected results with non-normalized integer columns

["Sergey Shelukhin (JIRA)" <ji...@apache.org>]

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

Sergey Shelukhin commented on HIVE-6052:
----------------------------------------

rb at https://reviews.apache.org/r/16339/

> 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
>         Attachments: 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)