czy006 opened a new issue, #3119: URL: https://github.com/apache/amoro/issues/3119
### Search before asking - [X] I have searched in the [issues](https://github.com/apache/amoro/issues?q=is%3Aissue) and found no similar issues. ### What would you like to be improved? Users need to manually calculate thousands of values/memory units every time. If it can be similar to the [Apache Flink configuration](https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/deployment/config/#duration), users can complete the configuration by specifying values with memory units/time units, which will greatly facilitate the user experience. for **self-optimizing.minor.trigger.interval** as an example Before - self-optimizing.minor.trigger.interval - 3600000(1 hour) - The time interval in milliseconds to trigger minor optimizing After - self-optimizing.minor.trigger.duration - 1hour/1day [0-9]+ (d | day | h | hour | m | min | minute | s | sec | second | ms | milli | millisecond | us | micro | microsecond | ns | nano | nanosecond) - Duration The time interval Duration to trigger minor optimizing The before configuration will be removed in 0.9. We can recommend users to modify the configuration as soon as possible, and it should be noted in the upgrade log. ### How should we improve? - add duration config support - add unit test with new duration config - Ensure compatibility of old configurations, and new configurations have higher priority ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Subtasks _No response_ ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
