nada-attia opened a new pull request, #18145: URL: https://github.com/apache/hudi/pull/18145
### Describe the issue this Pull Request addresses When cleans and archivals are disabled on the data table, these operations should also be disabled on the metadata table (MDT). Currently, the MDT does not respect these settings and continues to perform archival and clean operations even when they are disabled on the main table. ### Summary and Changelog **Summary:** When `hoodie.clean.automatic` or `hoodie.archive.automatic` are set to false on the data table, the metadata table should respect these settings and skip the corresponding operations. **Changelog:** - Modified `HoodieBackedTableMetadataWriter.performTableServices()` to check `dataWriteConfig.isAutoClean()` before running clean operations on MDT - Modified `HoodieBackedTableMetadataWriter.performTableServices()` to check `dataWriteConfig.isAutoArchive()` before running archive operations on MDT - Added unit test `testArchivalAndCleanRespectDataTableSettings` with parameterized test cases covering all combinations of autoClean/autoArchive settings ### Impact This change affects metadata table maintenance behavior. When auto clean or auto archive is disabled on the data table, the corresponding operations will now also be skipped on the metadata table. This is the expected behavior since MDT should follow the data table's configuration. No public API changes. ### Risk Level low The change is straightforward conditional checks that respect existing configuration settings. Unit tests have been added to verify the behavior. ### Documentation Update none The configs `hoodie.clean.automatic` and `hoodie.archive.automatic` already exist. This PR just ensures MDT respects these settings. ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [x] 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]
