cshuo opened a new issue, #19358:
URL: https://github.com/apache/hudi/issues/19358

   ## Task Description
   
   **What needs to be done:**
   
   Improve unit-test coverage for metadata-table read paths in `hudi-common`, 
especially for metadata-enabled table fixtures and branch-heavy utility logic. 
The primary classes in scope are:
   
   - `HoodieTableMetadataUtil`
   - `HoodieBackedTableMetadata`
   - `HoodieMetadataPayload`
   - `BaseTableMetadata`
   - `FileSystemBackedTableMetadata`
   - `MetadataPartitionType`
   - `BaseFileRecordParsingUtils`
   
   Add focused tests for normal reads, empty inputs, missing partitions, 
unsupported index versions, file-list and statistics handling, rollback/restore 
behavior, secondary-index reads, reusable readers, and error propagation. Raise 
each target class to at least 92% line coverage and include before/after 
per-class coverage in the PR.
   
   While adding coverage, verify index-definition lookup behavior for 
expression and secondary indexes. The lookup helper accepts `(indexType, 
sourceField)`, but the current callers pass these values in the opposite order, 
causing an existing matching definition to be treated as missing.
   
   **Why this task is needed:**
   
   The metadata read package contains a large number of uncovered branches, 
including behavior used only when the metadata table and optional indexes are 
enabled. These gaps make regressions in record generation, file listing, 
statistics retrieval, index initialization, and failure handling harder to 
detect. The reversed index-definition lookup arguments also break idempotent 
detection of existing expression and secondary index definitions.
   
   ## Task Type
   
   Test enhancement
   
   ## Related Issues
   
   **Parent feature issue:** N/A
   
   **Related issues:** N/A
   


-- 
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]

Reply via email to