You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "hehuiyuan (Jira)" <ji...@apache.org> on 2022/07/07 03:09:00 UTC
[jira] [Commented] (FLINK-26848) JDBC don't flush data when disable flush-max-rows and flush-interval
[ https://issues.apache.org/jira/browse/FLINK-26848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563552#comment-17563552 ]
hehuiyuan commented on FLINK-26848:
-----------------------------------
Hi [~jark] , have time to look at this issues?
> JDBC don't flush data when disable flush-max-rows and flush-interval
> --------------------------------------------------------------------
>
> Key: FLINK-26848
> URL: https://issues.apache.org/jira/browse/FLINK-26848
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Reporter: hehuiyuan
> Assignee: hehuiyuan
> Priority: Minor
> Labels: pull-request-available, stale-assigned
> Attachments: image-2022-03-24-22-05-23-717.png
>
>
> ||h5. sink.buffer-flush.interval||The flush interval mills, over this time, asynchronous threads will flush data. Can be set to {{'0'}} to disable it. Note, {{'sink.buffer-flush.max-rows'}} can be set to {{'0'}} with the flush interval set allowing for complete async processing of buffered actions.||
> |h5. sink.buffer-flush.max-rows|The max size of buffered records before flush. Can be set to zero to disable it.|
>
> h5. `Asynchronous thread flush` is disabled when set `sink.buffer-flush.interval` = 0, then disable `sink.buffer-flush.max-rows`, which causes the data is not written out.
> The data are not written when disable `flush.interval` and `max-rows`. I think it should write out when the data arrive.
> !image-2022-03-24-22-05-23-717.png|width=740,height=360!
>
> h5.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)