cshuo opened a new pull request, #18399:
URL: https://github.com/apache/hudi/pull/18399

   ### Describe the issue this Pull Request addresses
   
   This PR tightens HoodieTableFactory validation so unsupported RLI 
initialization behavior is rejected early with a clear error, and aligns 
related validation messages to use concrete option keys. 
   
   ### Summary and Changelog
   - Updated `HoodieTableFactory` validation for `GLOBAL_RECORD_LEVEL_INDEX` to 
explicitly reject deferred RLI initialization by checking 
`HoodieMetadataConfig.DEFER_RLI_INIT_FOR_FRESH_TABLE`.
   - Added/updated `TestHoodieTableFactory` coverage to assert 
`IllegalArgumentException` when deferred RLI init is enabled for global 
record-level index in Flink.
   
   ### Impact
   - **Functional impact**: Flink table creation now fails fast for unsupported 
`GLOBAL_RECORD_LEVEL_INDEX + deferred RLI init` configuration.
   
   ### Risk Level
   low
   
   <!-- Accepted values: none, low, medium or high. Other than `none`, explain 
the risk.
        If medium or high, explain what verification was done to mitigate the 
risks. -->
   
   ### Documentation Update
   
   <!-- Describe any necessary documentation update if there is any new 
feature, config, or user-facing change. If not, put "none".
   
   - The config description must be updated if new configs are added or the 
default value of the configs are changed.
   - Any new feature or user-facing change requires updating the Hudi website. 
Please follow the 
     [instruction](https://hudi.apache.org/contribute/developer-setup#website) 
to make changes to the website. -->
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Enough context is provided in the sections above
   - [ ] Adequate tests were added if applicable
   


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