lintingbin commented on PR #3193: URL: https://github.com/apache/amoro/pull/3193#issuecomment-2343168502
> @lintingbin Thanks for the contribution. > > The scheduling interval for the current expiration task is usually set as an AMS configuration like `data-expiration.interval`, which applies to all tables. I think this meets the requirements, as we generally do not adjust different execution interval for different tables. What do you think? > > BTW, we are improving the configuration value for time duration with unit support like 3d, we can do it for the new configuration. The modifications have been completed according to the suggestions. -- 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]
