Sagar Sumit created HUDI-8326:
---------------------------------

             Summary: Improve functional index tests
                 Key: HUDI-8326
                 URL: https://issues.apache.org/jira/browse/HUDI-8326
             Project: Apache Hudi
          Issue Type: Task
            Reporter: Sagar Sumit
            Assignee: Sagar Sumit
             Fix For: 1.0.0


[https://github.com/apache/hudi/pull/12069#issuecomment-2400846952]

`TestFunctionalIndex` currently covers the following:
 # Index initialization and drop for cow/mor.
 # Index enable and disable for cow.
 # Index non-partitioned table and hive sync for mor.
 # Upsert after initialization for cow/mor.

We need to ensure that we cover the following cases too:
 # insert few records validate. update the same and validate updates are 
reflected. repeat the updates and validate stats.
for MOR, trigger compaction and validate.
 # trigger clustering on top of 1 and validate stats. a. for MOR, lets trigger 
clustering before compaction and also after compaction. ensure that no stats 
are available for the replaced file groups.
 # insert few records, update. and delete subset of records which should impact 
the min and max values. validate.
 # lets add a test for async compaction and validate. i.e. some log files are 
added to new phantom file slice and stats are intact.
 # lets have a test for non partitioned table.
 # lets trigger rollbacks and validate. i.e. insert, update (partially failed). 
validate that only stats pertianing to inserts are reflected. trigger a 
rollback and validate its still the same. retry the updates. stats should 
reflect stats w/ updated records.
 # lets add one long running tests. i.e with 20+ commits and aggressive cleaner 
and archival. just for sanity. or if we can enable all kinds of index in an 
existing sanity tests, I am good.
 # lets test all write operations. bulk_insert, insert, upsert, delete, 
insert_overwrite, insert_overwrite_table, delete_partition.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to