[ 
https://issues.apache.org/jira/browse/HIVE-29724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105403#comment-18105403
 ] 

Zhihua Deng commented on HIVE-29724:
------------------------------------

In current master, adding partitions or renaming tables 
[HIVE-28972|https://issues.apache.org/jira/browse/HIVE-28972] will force the 
partitions reuse the current table's schema, so we shouldn't see the column 
metadata bloat in a normal Metastore per my understanding.

I would prefer for adding this as an one-off command, executed post upgrade or 
replication. After that,  the code itself will handle the de-duplicating the 
columns while adding new partitions.

> Provide a Metastore tool for de-duplicating the columns
> -------------------------------------------------------
>
>                 Key: HIVE-29724
>                 URL: https://issues.apache.org/jira/browse/HIVE-29724
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Zhihua Deng
>            Priority: Major
>
> Following the discussion on HIVE-29694, we can provide a tool to de-duplicate 
> the columns to avoid column metadata bloat, which could happen during 
> replication.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to