[
https://issues.apache.org/jira/browse/HIVE-29724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106087#comment-18106087
]
Zhihua Deng edited comment on HIVE-29724 at 8/19/26 11:48 PM:
--------------------------------------------------------------
What I'm trying to explain is making the de-duplicating tool as a maintenance
thread running at specific intervals is costly and unnecessary.
As of now in current master branch, we have enforced the partition to re-use
the table's schema either upon the table schema evolution or by adding new
partitions.
This de-duplicating command should just run post the replication or upgrade, or
at specific maintenance window.
was (Author: dengzh):
What I'm trying to explain is making the de-duplicating tool as a maintenance
thread running at specific intervals is costly and unnecessary.
As of now in current master branch, we have enforced the partition to re-use
the table's schema either upon the table schema evolution or by adding new
partitions.
This de-duplicating command should just run post the replication or upgrade, or
at specified maintenance window.
> 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)
