[ https://issues.apache.org/jira/browse/FLINK-16328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-16328: ----------------------------------- Labels: stale-minor (was: ) > Restart batch timer in JDBC sink after successful execution > ----------------------------------------------------------- > > Key: FLINK-16328 > URL: https://issues.apache.org/jira/browse/FLINK-16328 > Project: Flink > Issue Type: Improvement > Components: Connectors / JDBC > Affects Versions: 1.10.0 > Reporter: Roman Khachatryan > Priority: Minor > Labels: stale-minor > > During the review of [https://github.com/apache/flink/pull/11061] > the following issue was discovered by [~kkl0u] : > {quote}Here shouldn't we restart the timer? It seems like we may be in the > situation where we flushed this batch because we reached the max size, so for > the new one we have to set a new timer (renew the BatchIntervalMs), right? > {quote} > -- This message was sent by Atlassian Jira (v8.3.4#803005)