eemario opened a new issue, #1378: URL: https://github.com/apache/flink-agents/issues/1378
### Search before asking - [x] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description Flink Agents uses different units for numeric duration settings. For example, `async.batch.timeout.ms` uses milliseconds, while `retry-wait-interval` uses seconds. It would be better to follow Flink’s approach and use dedicated duration types to make these settings easier to read and reduce unit conversion errors. [FLIP-442](https://cwiki.apache.org/confluence/spaces/FLINK/pages/300026759/FLIP-442%2BGeneral%2BImprovement%2Bto%2BConfiguration%2Bfor%2BFlink%2B2.0) For Flink Agents, we could use `java.time.Duration` in Java and `datetime.timedelta` in Python. - **Framework configuration.** Standardize how users configure durations in Java and Python. - **Built-in resource configuration.** Review existing duration parameters and decide case by case whether to use the same duration types as the framework or align with the corresponding SDK’s configuration. This work should be completed for 1.0, when Flink Agents plans to start guaranteeing API compatibility. ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
