hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-11726) Pushed IN predicates to the metastore
Date Tue, 03 Nov 2015 21:46:27 GMT


Hive QA commented on HIVE-11726:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 9767 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
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: 4 tests failed

This message is automatically generated.

ATTACHMENT ID: 12770355 - PreCommit-HIVE-TRUNK-Build

> Pushed IN predicates to the metastore
> -------------------------------------
>                 Key: HIVE-11726
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>         Attachments: HIVE-11726.01.patch, 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 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

View raw message