Bug Description
What happened:
HoodieBackedTableMetadataWriter#initializeFileGroups initializes every metadata table file group by writing an empty HoodieDeleteBlock in the legacy inline log format. When native log format is enabled by default, MDT expects native .log.hfile files, so an empty file group may not be discovered by the file-system view before it receives records.
What you expected:
When native log format is enabled, initialize each empty MDT file group with a zero-record native .log.hfile containing the instant time, writer schema, and native log version in footer metadata. Continue using the empty inline delete block for legacy log format.
Steps to reproduce:
- Enable the metadata table with a table version that writes native logs.
- Initialize an MDT partition with file groups that receive no records during bootstrap.
- Load the metadata table file-system view.
- Observe that file groups without a native log file are not discovered.
Environment
Hudi version: current master
Query engine: engine-independent metadata table initialization
Relevant configs: native log format enabled
Related Issues
Parent feature issue: #14310
Bug Description
What happened:
HoodieBackedTableMetadataWriter#initializeFileGroupsinitializes every metadata table file group by writing an emptyHoodieDeleteBlockin the legacy inline log format. When native log format is enabled by default, MDT expects native.log.hfilefiles, so an empty file group may not be discovered by the file-system view before it receives records.What you expected:
When native log format is enabled, initialize each empty MDT file group with a zero-record native
.log.hfilecontaining the instant time, writer schema, and native log version in footer metadata. Continue using the empty inline delete block for legacy log format.Steps to reproduce:
Environment
Hudi version: current master
Query engine: engine-independent metadata table initialization
Relevant configs: native log format enabled
Related Issues
Parent feature issue: #14310