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/03 18:12:18 UTC

[GitHub] [hudi] nsivabalan edited a comment on issue #3394: [SUPPORT] Question on hudis default behaviour for UPSERT

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


   yeah, with global index use-case, especially when there is a clash between two records just wrt partition path, depending on the [config value](https://hudi.apache.org/docs/configurations#bloomindexupdatepartitionpathupdatepartitionpath--false) set, hudi does either of these two. 
   a. delete existing storage record in old partition and insert to new partition
   or 
   b. update incoming record to same old partition (ignoring the new partition.
   
   In this flow hudi does not honor preCombine. 
   PreCombine will be honored when a updates happen. for eg (b) in above scenario.
   


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