hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chaoyu Tang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-15530) Optimize the column stats update logic in table alteration
Date Wed, 11 Jan 2017 14:38:58 GMT

     [ https://issues.apache.org/jira/browse/HIVE-15530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chaoyu Tang updated HIVE-15530:
-------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0
           Status: Resolved  (was: Patch Available)

Committed to branch 2.2.0. Thanks [~Yibing] for the patch, [~aihuaxu] and [~pxiong] for reviews.

> 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
>            Reporter: Yibing Shi
>            Assignee: Yibing Shi
>             Fix For: 2.2.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.3.4#6332)

Mime
View raw message