[HUDI-499] Allow partition path to be updated with GLOBAL_BLOOM index

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Implemented
• Fix Version/s: 0.5.2
• Component/s: index
• Labels: pull-request-available
• Assignee: Raymond Xu
• Reporter: Raymond Xu
• Created: 04/Jan/20 17:20
• Updated: 25/Mar/20 10:13
• Resolved: 05/Feb/20 21:00

Description

Context

When a record is to be updated with a new partition path, and when set to GLOBAL_BLOOM as index, the current logic implemented in https://github.com/apache/incubator-hudi/pull/1091/ ignores the new partition path and update the record in the original partition path.

Proposed change

Allow records to be inserted into their new partition paths and delete the records in the old partition paths. A configuration (e.g. hoodie.index.bloom.update.partition.path=true) can be added to enable this feature.

An example use case

A Hudi dataset manages people info and partitioned by birthday. In most cases, where people info are updated, birthdays are not to be changed (that's why we choose it as partition field). But in some edge cases where birthday info are input wrongly and we want to manually fix it or allow user to updated it occasionally. In this case, option 2 would be helpful in keeping records in the expected partition, so that a query like "show me people who were born after 2000" would work.

 

Issue Links

• relates to: HUDI-389 Updates sent to diff partition for a given key with Global Index
• links to: Dev email discussion
• links to: GitHub Pull Request #1187
• links to: GitHub Pull Request #1190