[
https://issues.apache.org/jira/browse/HUDI-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706864#comment-17706864
]
kazdy edited comment on HUDI-6006 at 3/30/23 1:04 PM:
------------------------------------------------------
[~ljain] as a user of "hoodie.payload.ordering.field" that helps me to apply
merge logic to my tables with default hudi payload I am concerned and would
like to ask why this is considered a bug?
precombine was for deduplicating incoming data
ordering field was for specifying what column is used to decide what records to
merge to the table
the ordering field can be changed and precombine can not, therefore it was
preferred to use it to introduce "business meaning" to which records to merge
If hoodie.payload.ordering.field is deprecated, how do I preserve the behavior
when writing to hudi with default payload when precombine field can not be
changed?
was (Author: JIRAUSER284048):
[~ljain] as a user of "hoodie.payload.ordering.field" that helps me to apply
merge logic to my tables with default hudi payload I am concerned and would
like to ask why this is considered a bug?
precombine was for deduplicating incoming data
ordering field was for specifying what column is used to decide what records to
merge to the table
the ordering field can be changed and precombine can not, therefore it was
preferred to use it to introduce "business meaning" to which records to merge
If hoodie.payload.ordering.field is deprecated, how do I preserve the behavior
when writing to hudi with default payload?
> Deprecate "hoodie.payload.ordering.field"
> -----------------------------------------
>
> Key: HUDI-6006
> URL: https://issues.apache.org/jira/browse/HUDI-6006
> Project: Apache Hudi
> Issue Type: Bug
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Labels: pull-request-available
>
> The jira aims to deprecate "hoodie.payload.ordering.field" and use preCombine
> config instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
