You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Lin Liu (Jira)" <ji...@apache.org> on 2024/12/09 23:16:00 UTC

[jira] [Commented] (HUDI-8409) Ensure that upgrade and downgrade work with merging configs

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

Lin Liu commented on HUDI-8409:
-------------------------------

So far I have tested the upgrade path. What I found is that:
 # For MOR table, either we use `DefaultHoodieRecordPayload` or `OverwriteWithLatestPayload`, it will be transformed into EventTimeOrdering with `DefaultHoodieRecordPayload` payload.
 # For COW table, even we use `OverwriteWithLatestPayload` class, the table properties from 0.15.0 does not record this information. Therefore, after upgraded to 1.0.0, it is treated as default.

> Ensure that upgrade and downgrade work with merging configs
> -----------------------------------------------------------
>
>                 Key: HUDI-8409
>                 URL: https://issues.apache.org/jira/browse/HUDI-8409
>             Project: Apache Hudi
>          Issue Type: Task
>            Reporter: Jonathan Vexler
>            Assignee: Lin Liu
>            Priority: Blocker
>             Fix For: 1.0.1
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> Make sure that we are upgrading and downgrading correctly with the merge configs such as payload class and merge mode



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