You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Rahil Chertara (Jira)" <ji...@apache.org> on 2025/07/29 00:10:00 UTC
[jira] [Assigned] (HUDI-9658) Improve Upgrade/Downgrade issues in event of crash
[ https://issues.apache.org/jira/browse/HUDI-9658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahil Chertara reassigned HUDI-9658:
------------------------------------
Assignee: Rahil Chertara
> Improve Upgrade/Downgrade issues in event of crash
> --------------------------------------------------
>
> Key: HUDI-9658
> URL: https://issues.apache.org/jira/browse/HUDI-9658
> Project: Apache Hudi
> Issue Type: Bug
> Reporter: Rahil Chertara
> Assignee: Rahil Chertara
> Priority: Major
>
> Currently today in our upgrade/downgrade logic, if a hudi table contains a metadata table, we first upgrade/downgrade this table before proceeding to the data table. However if there is a crash in the process for mdt table, we have a silent failure but continue to upgrade/downgrade data table which can cause these two tables version to be out of sync.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)