[
https://issues.apache.org/jira/browse/HUDI-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889808#comment-17889808
]
Lokesh Jain commented on HUDI-8203:
-----------------------------------
Open items for discussion:
# Backwards compatibility of new merger configs and the changes in table
configs.
# Upgrade handling with the new configs
# Should the user be allowed to change merge mode/payload?
# Avro read path depends upon payload type for merging. Do we need merge mode
handling here?
# HoodieMergeConfig - Can we handle this change in a separate PR? This can
bring more changes t{{{}{}}}o this PR.
# Do we want to deprecate payload type config for beta release? Is it ok to
remove the config for the GA release?
> Make record merge mode the primary merging config
> -------------------------------------------------
>
> Key: HUDI-8203
> URL: https://issues.apache.org/jira/browse/HUDI-8203
> Project: Apache Hudi
> Issue Type: Improvement
> Components: reader-core
> Reporter: Jonathan Vexler
> Assignee: Jonathan Vexler
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.0.0
>
> Original Estimate: 32h
> Time Spent: 28h
> Remaining Estimate: 4h
>
> Make record merge mode the primary config for merging. Only use payload if
> custom merge mode is used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
