You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "zhangdonglin (Jira)" <ji...@apache.org> on 2022/06/17 06:37:00 UTC
[jira] [Updated] (HIVE-26335) Partition params dit not updated after calling Hive.loadPartition
[ https://issues.apache.org/jira/browse/HIVE-26335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhangdonglin updated HIVE-26335:
--------------------------------
Description:
Hi,
I found that when partition A already exists, after calling Hive.loadPartition to load data into partition A, the partition params in table PARTITION_PARAMS was not updated. even I set hasFollowingStatsTask=false.
The reason is below, newTPart was set to oldPart when old partition exists,
{code:java}
Partition newTPart = oldPart != null ? oldPart : new Partition(tbl, partSpec, newPartPath); {code}
Due to this, when calling alter_partition, oldPart info was send to metastore and it will not update partition params.
was:
Hi,
I found that when partition A already exists, after calling Hive.loadPartition to load data into partition A, the partition params in table PARTITION_PARAMS was not updated. even I set hasFollowingStatsTask=false.
The reason is below, newTPart was set to oldPart,
{code:java}
Partition newTPart = oldPart != null ? oldPart : new Partition(tbl, partSpec, newPartPath); {code}
Due to this, when calling alter_partition, oldPart info was send to metastore and it will not update partition params.
> Partition params dit not updated after calling Hive.loadPartition
> -----------------------------------------------------------------
>
> Key: HIVE-26335
> URL: https://issues.apache.org/jira/browse/HIVE-26335
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: All Versions
> Reporter: zhangdonglin
> Priority: Major
>
> Hi,
> I found that when partition A already exists, after calling Hive.loadPartition to load data into partition A, the partition params in table PARTITION_PARAMS was not updated. even I set hasFollowingStatsTask=false.
> The reason is below, newTPart was set to oldPart when old partition exists,
> {code:java}
> Partition newTPart = oldPart != null ? oldPart : new Partition(tbl, partSpec, newPartPath); {code}
> Due to this, when calling alter_partition, oldPart info was send to metastore and it will not update partition params.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)