[
https://issues.apache.org/jira/browse/HUDI-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904290#comment-17904290
]
Lin Liu edited comment on HUDI-8409 at 12/9/24 11:29 PM:
---------------------------------------------------------
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, which is as expected.
# For COW table, even we use `OverwriteWithLatestPayload` class, the table
properties from 0.15.0 does not record this information (payload class).
Therefore, after upgraded to 1.0.0, it is treated as event time based.
So, for 0.15.0, there is no way to upgrade a table into COMMIT_TIME_ORDERING
mode.
I will test 0.14.x to see if this is still true.
was (Author: JIRAUSER301185):
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)
