hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Commented] (HIVE-3959) Update Partition Statistics in Metastore Layer
Date Thu, 15 Oct 2015 01:40:05 GMT


Sergey Shelukhin commented on HIVE-3959:

hive.stats.reliable has a different, unrelated meaning as per documentation, so there's no
reason to check it for this case; hive.stats.autogather seems to be the right setting to control
automatic gathering of stats.
It can be disabled on systems like S3

> Update Partition Statistics in Metastore Layer
> ----------------------------------------------
>                 Key: HIVE-3959
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore, Statistics
>            Reporter: Bhushan Mandhani
>            Assignee: Ashutosh Chauhan
>            Priority: Minor
>             Fix For: 0.13.0
>         Attachments: HIVE-3959.1.patch, HIVE-3959.2.patch, HIVE-3959.3.patch, HIVE-3959.3.patch,
HIVE-3959.4.patch, HIVE-3959.4.patch, HIVE-3959.5.patch, HIVE-3959.6.patch, HIVE-3959.patch.1,
HIVE-3959.patch.11.txt, HIVE-3959.patch.12.txt, HIVE-3959.patch.2
> When partitions are created using queries ("insert overwrite" and "insert into") then
the StatsTask updates all stats. However, when partitions are added directly through metadata-only
partitions (either CLI or direct calls to Thrift Metastore) no stats are populated even if
hive.stats.reliable is set to true. This puts us in a situation where we can't decide if stats
are truly reliable or not.
> We propose that the "fast stats" (numFiles and totalSize) which don't require a scan
of the data should always be populated and be completely reliable. For now we are still excluding
rowCount and rawDataSize because that will make these operations very expensive. Currently
they are quick metadata-only ops.  

This message was sent by Atlassian JIRA

View raw message