bhasudha commented on code in PR #10080: URL: https://github.com/apache/hudi/pull/10080#discussion_r1396826530
########## website/docs/indexing.md: ########## @@ -155,4 +155,11 @@ to finally check the incoming updates against all files. The `SIMPLE` Index will `HBASE` index can be employed, if the operational overhead is acceptable and would provide much better lookup times for these tables. When using a global index, users should also consider setting `hoodie.bloom.index.update.partition.path=true` or `hoodie.simple.index.update.partition.path=true` to deal with cases where the -partition path value could change due to an update e.g users table partitioned by home city; user relocates to a different city. These tables are also excellent candidates for the Merge-On-Read table type. \ No newline at end of file +partition path value could change due to an update e.g users table partitioned by home city; user relocates to a different city. These tables are also excellent candidates for the Merge-On-Read table type. + + +## Related Resources +<h3>Videos</h3> + +* [Global Bloom Index: Remove duplicates & guarantee uniquness - Hudi Labs](https://youtu.be/XlRvMFJ7g9c) +* [Advantages of Metadata Indexing and Asynchronous Indexing in Hudi - Hands on Lab](https://www.youtube.com/watch?v=TSphQCsY4pY) Review Comment: First one is okay. Lets move second over to there. -- 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]
