You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Micah Whitacre (JIRA)" <ji...@apache.org> on 2017/10/04 20:22:00 UTC
[jira] [Updated] (HIVE-15530) Optimize the column stats update
logic in table alteration
[ https://issues.apache.org/jira/browse/HIVE-15530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Micah Whitacre updated HIVE-15530:
----------------------------------
Component/s: Metastore
> Optimize the column stats update logic in table alteration
> ----------------------------------------------------------
>
> Key: HIVE-15530
> URL: https://issues.apache.org/jira/browse/HIVE-15530
> Project: Hive
> Issue Type: Bug
> Components: Hive, Metastore
> Reporter: Yibing Shi
> Assignee: Yibing Shi
> Fix For: 2.3.0
>
> Attachments: HIVE-15530.1.patch, HIVE-15530.2.patch, HIVE-15530.3.patch, HIVE-15530.4.patch, HIVE-15530.5.patch
>
>
> Currently when a table is altered, if any of below conditions is true, HMS would try to update column statistics for the table:
> # database name is changed
> # table name is changed
> # old columns and new columns are not the same
> As a result, when a column is added to a table, Hive also tries to update column statistics, which is not necessary. We can loose the last condition by checking whether all existing columns are changed or not. If not, we don't have to update stats info.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)