[
https://issues.apache.org/jira/browse/HIVE-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853321#comment-13853321
]
Hive QA commented on HIVE-6052:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12619620/HIVE-6052.02.patch
{color:green}SUCCESS:{color} +1 4795 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/704/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/704/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12619620
> 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.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)
