[GitHub] [hudi] ChaladiMohanVamsi commented on issue #3394: [SUPPORT] Question on hudi's default behaviour for UPSERT

[GitBox <gi...@apache.org>]

ChaladiMohanVamsi commented on issue #3394:
URL: https://github.com/apache/hudi/issues/3394#issuecomment-926697926


   @nsivabalan 
   But recently we also added another payload impl called DefaultHoodieRecordPayload. This payload will honor preCombine field while reconciling an incoming record with whats in storage using the preCombine field value(within combineAndGetUpdateValue()).
   
   I have a confusion on similar lines. Can you please clarify and correct my understanding.
   
   How are following config differ in DefaultHoodieRecordPayload, which config will it choose to select record.
   
   1. hoodie.payload.ordering.field
   2. hoodie.datasource.write.precombine.field
   
   With the same payload class is there a possibility to disable precombine during deduplicating in same incremental batch but allow deciding whether or not to update existing record.
   
   I tried DefaultHoodiePayload class with
   hoodi.combine.before.insert=false and not providing precombine field but has payload.ordering.field.
   
   In this scenario it thrower an error of missing precombine field column.


-- 
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: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org