hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-5483) use metastore statistics to optimize max/min/etc. queries
Date Sat, 19 Oct 2013 18:14:42 GMT


Hive QA commented on HIVE-5483:

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

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 4428 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.

> use metastore statistics to optimize max/min/etc. queries
> ---------------------------------------------------------
>                 Key: HIVE-5483
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Sergey Shelukhin
>            Assignee: Ashutosh Chauhan
>         Attachments: HIVE-5483.patch
> We have discussed this a little bit.
> Hive can answer queries such as select max(c1) from t purely from metastore using partition
statistics, provided that we know the statistics are up to date.
> All data changes (e.g. adding new partitions) currently go thru metastore so we can track
up-to-date-ness. If they are not up-to-date, the queries will have to read data (at least
for outdated partitions) until someone runs analyze table. We can also analyze new partitions
after add, if that is configured/specified in the command.

This message was sent by Atlassian JIRA

View raw message