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

["sunjincheng (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-16497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17120532#comment-17120532 ] 

sunjincheng commented on FLINK-16497:
-------------------------------------

+1 for thi,s as I mentioned in FLINK-18041, and I prefer 1 row as default as it's pretty friendly for user testing.

> 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
>            Priority: Major
>             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)