You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by GitBox <gi...@apache.org> on 2021/08/25 20:40:43 UTC

[GitHub] [hudi] maddy2u edited a comment on issue #3394: [SUPPORT] Question on hudi's default behaviour for UPSERT

maddy2u edited a comment on issue #3394:
URL: https://github.com/apache/hudi/issues/3394#issuecomment-905846390


   Hi Sivabalan,
   
   I work with Diego on this topic and I have one question regarding your response - 
   
   1. We use Hudi 0.7 on AWS Glue for processing and storing data. Based on what you mentioned, my understanding is that the below statement would not be applicable for this version of Hudi. Is it available in 0.8 or please correct my assumption? How do we enable us to use precombine field while reconciling an incoming record? Any edge scenarios that we must be aware of ?
   
   > 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()).
   
   
   Summarizing the discussion from this thread - 
   
   1. Hudi will always treat the new data coming in as the data that needs to overwrite. The data is always updated based on the new data that is coming in (implemented in OverwriteWithLatestAvroPayload)
   2. Depending on hoodie.simple.index.update.partition.path = true/false, the data will be updated in the old or new partitions.
   
   
   


-- 
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