You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/03/09 03:43:00 UTC

[jira] [Created] (FLINK-16497) Improve default flush strategy for JDBC sink to make it work out-of-box

Jark Wu created FLINK-16497:
-------------------------------

             Summary: Improve default flush strategy for JDBC sink to make it work out-of-box
                 Key: FLINK-16497
                 URL: https://issues.apache.org/jira/browse/FLINK-16497
             Project: Flink
          Issue Type: Improvement
          Components: Connectors / JDBC, Table SQL / Ecosystem
            Reporter: Jark Wu
             Fix For: 1.11.0


Currently, JDBC sink provides 2 flush options:

{code}
'connector.write.flush.max-rows' = '5000', -- default is 5000
'connector.write.flush.interval' = '2s', -- no default value
{code}

That means if flush interval is not set, the buffered output rows may not be flushed to database for a long time. That is a surprising behavior because no results are outputed by default. 

So I propose to have a default flush '1s' interval for JDBC sink or default 1 row for flush size. 







--
This message was sent by Atlassian Jira
(v8.3.4#803005)