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 2019/11/27 18:45:30 UTC

[GitHub] [incubator-hudi] vinothchandar commented on issue #1052: [HUDI-326] Add new index to suppport global update/delete

vinothchandar commented on issue #1052: [HUDI-326] Add new index to suppport global update/delete
URL: https://github.com/apache/incubator-hudi/pull/1052#issuecomment-559208611
 
 
   > I have seen the JIRA that wants to set the HoodieIndex as part of the table properties. This conflicts with the usecase here. Can you help me understand the motivation of locking down the index type?
   
   The thinking was that if someone writes few commits using `HoodieBloomIndex` and then later switches to `HoodieGlobalBloomIndex` for e.g , then it won't guarantee globally unique keys as he/she might expect, since the first set of commits may have duplicates across partitions. If you take HBaseIndex,  that's another clear example, user cannot just switch from HoodieBloomIndex to HBase without rebuilding the index first?
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services