You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Udit Mehrotra (Jira)" <ji...@apache.org> on 2021/08/25 02:02:00 UTC
[jira] [Updated] (HUDI-1932) Hive Sync should not always update
last_commit_time_sync
[ https://issues.apache.org/jira/browse/HUDI-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Udit Mehrotra updated HUDI-1932:
--------------------------------
Fix Version/s: (was: 0.9.0)
0.10.0
> Hive Sync should not always update last_commit_time_sync
> --------------------------------------------------------
>
> Key: HUDI-1932
> URL: https://issues.apache.org/jira/browse/HUDI-1932
> Project: Apache Hudi
> Issue Type: Bug
> Components: Hive Integration
> Reporter: Raymond Xu
> Assignee: nate radtke
> Priority: Major
> Labels: AWS, pull-request-available
> Fix For: 0.10.0
>
>
> In Hive SyncÂ
> {{org.apache.hudi.hive.HiveSyncTool#syncHoodieTable()}}
> it includes schema update and partition update.
> Regardless of having update or not, the logic is to always update the table with a new timestamp for the last_commit_time_sync property.
> This will result in having new versions in AWS Glue tables for example, which will eventually lead to exceeding table version limit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)