You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Roman Khachatryan (Jira)" <ji...@apache.org> on 2020/02/28 08:59:00 UTC

[jira] [Updated] (FLINK-16328) Restart batch timer in JDBC sink

     [ https://issues.apache.org/jira/browse/FLINK-16328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Khachatryan updated FLINK-16328:
--------------------------------------
    Description: 
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}
 

  was:
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}
 


> Restart batch timer in JDBC sink
> --------------------------------
>
>                 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
>
> 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)