[HUDI-8534] Ensure index creation is idempotent in face of failures

• Type: Task
• Status: Patch Available
• Priority: Blocker
• Resolution: Unresolved
• Fix Version/s: 1.0.0
• Labels: pull-request-available
• Epic Link: secondary index
• Assignee: Lokesh Jain
• Reporter: Vinoth Chandar

Reviewers

Sagar Sumit

• Created: 17/Nov/24 19:10
• Updated: 41 minutes ago

Description

We need to ensure the user can execute `CREATE INDEX name ...`. with same name, failing many times and then be able to eventually succeed with the right syntax/parameters. 

spark-sql (default)> create index idx_bloom on hudi_table using bloom_filter(city) options(func='lower');

24/11/16 09:58:44 ERROR SparkSQLDriver: Failed in [create index idx_bloom on hudi_table using bloom_filter(city) options(func='lower')]
java.lang.IllegalArgumentException: The value of hoodie.functional.index.type should be one of COLUMN_STATS,BLOOM_FILTERS,SECONDARY_INDEX, but was bloom_filter

spark-sql (default)> create index idx_bloom on hudi_table using bloom_filters(city) options(func='lower');
24/11/16 09:59:11 ERROR SparkSQLDriver: Failed in [create index idx_bloom on hudi_table using bloom_filters(city) options(func='lower')]
java.lang.IllegalArgumentException: The value of hoodie.functional.index.type should be one of COLUMN_STATS,BLOOM_FILTERS,SECONDARY_INDEX, but was bloom_filter
 

Issue Links

• is a clone of: HUDI-8533 Bloom Functional Index creation without function fails
• is cloned by: HUDI-8541 Change to relative paths for the index defs json
• links to: GitHub Pull Request #12308