hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Updated] (HIVE-6157) Fetching column stats slower than the 101 during rush hour
Date Tue, 21 Jan 2014 23:14:23 GMT


Sergey Shelukhin updated HIVE-6157:

    Attachment: HIVE-6157.01.patch

first patch. There's one TODO# left where I think some validation code is dead, need to see
if any tests fail with it.

Other than that many tests I ran passed, let's see what HiveQA says

> Fetching column stats slower than the 101 during rush hour
> ----------------------------------------------------------
>                 Key: HIVE-6157
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.13.0
>            Reporter: Gunther Hagleitner
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-6157.01.patch, HIVE-6157.nogen.patch, HIVE-6157.prelim.patch
> "hive.stats.fetch.column.stats" controls whether the column stats for a table are fetched
during explain (in Tez: during query planning). On my setup (1 table 4000 partitions, 24 columns)
the time spent in semantic analyze goes from ~1 second to ~66 seconds when turning the flag
on. 65 seconds spent fetching column stats...
> The reason is probably that the APIs force you to make separate metastore calls for each
column in each partition. That's probably the first thing that has to change. The question
is if in addition to that we need to cache this in the client or store the stats as a single
blob in the database to further cut down on the time. However, the way it stands right now
column stats seem unusable.

This message was sent by Atlassian JIRA

View raw message