HsbcJone opened a new issue, #1384: URL: https://github.com/apache/flink-agents/issues/1384
### Search before asking - [x] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description This is the first slice of #1378 (standardize duration configuration), scoped to **framework configuration only**, as agreed in that thread after discussion with @wenjin272. Flink Agents currently uses bare numeric types, with the unit either in the key or only in the docs, and the units are not consistent. Known framework duration settings include: - `async.batch.timeout.ms` — `long` in milliseconds (`-1` disables it) - `short-term-memory.state-ttl.ms` — `long` in milliseconds (`0` disables it) - `retry-wait-interval` — `int` in seconds The goal is to follow Flink's [FLIP-442](https://cwiki.apache.org/confluence/spaces/FLINK/pages/300026759/FLIP-442%2BGeneral%2BImprovement%2Bto%2BConfiguration%2Bfor%2BFlink%2B2.0) approach and use dedicated duration types so these settings are easier to read and less error-prone: `java.time.Duration` in Java and `datetime.timedelta` in Python, with tests and docs kept in sync on both sides. Built-in resource / SDK-aligned duration parameters are out of scope here; those stay with #1378's second part. ### Are you willing to submit a PR? - [x] 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]
