hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-4914) filtering via partition name should be done inside metastore server (implementation)
Date Wed, 25 Sep 2013 04:14:02 GMT


Hive QA commented on HIVE-4914:

{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 3149 tests passed

Test results:
Console output:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.
> filtering via partition name should be done inside metastore server (implementation)
> ------------------------------------------------------------------------------------
>                 Key: HIVE-4914
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: D12561.5.patch, D12561.6.patch, D12561.7.patch, HIVE-4914.01.patch,
HIVE-4914.02.patch, HIVE-4914.03.patch, HIVE-4914.04.patch, HIVE-4914.05.patch, HIVE-4914.06.patch,
HIVE-4914.07.patch, HIVE-4914.D12561.1.patch, HIVE-4914.D12561.2.patch, HIVE-4914.D12561.3.patch,
HIVE-4914.D12561.4.patch, HIVE-4914.D12645.1.patch, HIVE-4914-only-no-gen.patch, HIVE-4914-only.patch,
HIVE-4914.patch, HIVE-4914.patch, HIVE-4914.patch
> Currently, if the filter pushdown is impossible (which is most cases), the client gets
all partition names from metastore, filters them, and asks for partitions by names for the
filtered set.
> Metastore server code should do that instead; it should check if pushdown is possible
and do it if so; otherwise it should do name-based filtering.
> Saves the roundtrip with all partition names from the server to client, and also removes
the need to have pushdown viability checking on both sides.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message