rangareddy commented on issue #17093:
URL: https://github.com/apache/hudi/issues/17093#issuecomment-5066309099
This issue was reviewed as part of the JIRA-migrated backlog triage.
Findings: this is a configuration-usage matter, not a bug - event-time
ordering works correctly when it is set via the documented write configs. In
the report the table-property keys were passed as write options:
hoodie.record.merge.mode=EVENT_TIME_ORDERING
hoodie.table.precombine.field=ts
Those are table-config keys and are not honored on the write path, so the
table fell back to COMMIT_TIME_ORDERING (and no precombine field was set),
which is what you observed in hoodie.properties.
Use the write configs instead:
hoodie.write.record.merge.mode=EVENT_TIME_ORDERING
hoodie.datasource.write.precombine.field=ts
Verified on Hudi 1.0.2: with the write configs the table is created with
hoodie.record.merge.mode=EVENT_TIME_ORDERING and the precombine field
populated; with the table-property keys it defaults to COMMIT_TIME_ORDERING.
See https://hudi.apache.org/docs/record_merger#record-merge-configs (also noted
by @yihua above).
If you still see an incorrect merge mode after switching to the write
configs, please reopen with details. Closing as resolved.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
