[
https://issues.apache.org/jira/browse/HIVE-11726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729631#comment-14729631
]
Hive QA commented on HIVE-11726:
--------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12754031/HIVE-11726.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 9393 tests executed
*Failed tests:*
{noformat}
org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5166/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5166/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-5166/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12754031 - PreCommit-HIVE-TRUNK-Build
> Pushed IN predicates created by PointLookupOptimizer to the metastore
> ---------------------------------------------------------------------
>
> Key: HIVE-11726
> URL: https://issues.apache.org/jira/browse/HIVE-11726
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Attachments: HIVE-11726.patch
>
>
> The PointLookupOptimizer can turn off some of the optimizations due to its
> use of tuple IN() clauses.
> HIVE-11573 introduced the extraction of sub-clauses that could be pushed down
> till the TableScan operators, though they wouldn't be pushed down to the
> metastore.
> In this issue, we tackle this problem by:
> 1) Grouping the columns in the sub-clauses depending on their lineage. This
> way PPD will be able to push them down throw the plan without any extension.
> For instance, if a, b, and c are partition columns, a and b belong to table1,
> and c belong to table2:
> {code}
> (a,b,c) IN ((1,2,3),(2,3,4)) ->
> (a,b) IN ((1,2),(2,3)) and c in (3,4) and (a,b,c) IN
> ((1,2,3),(2,3,4))
> {code}
> 2) Extending the filter parser of the metastore to support IN clauses,
> including multiple columns. This allows to push those additional predicates
> down throw directSQL to the metastore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
