[
https://issues.apache.org/jira/browse/FLINK-20979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556862#comment-17556862
]
Yankee24 commented on FLINK-20979:
----------------------------------
I see that the problem marked as starter has not been solved, I don't know if
you can assign this problem to me, I see the configuration of sink in the
connector sink.bulk-flush.max-actions, sink.bulk-flush.max-size and
sink.bulk-flush.interval should be set to 0 in the document to disable, should
you modify the ElasticsearchConfiguration.java in the code, and convert 0 to -1
in it
> Wrong description of 'sink.bulk-flush.max-actions'
> --------------------------------------------------
>
> Key: FLINK-20979
> URL: https://issues.apache.org/jira/browse/FLINK-20979
> Project: Flink
> Issue Type: Bug
> Components: Connectors / ElasticSearch, Documentation, Table SQL /
> Ecosystem
> Affects Versions: 1.12.0
> Reporter: Dawid Wysakowicz
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> pull-request-available, starter
>
> The documentation claims the option can be disabled with '0', but it can
> actually be disable with '-1' whereas '0' is an illegal value.
> {{Maximum number of buffered actions per bulk request. Can be set to '0' to
> disable it. }}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
