You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/04/07 22:39:00 UTC

[jira] [Updated] (FLINK-20979) Wrong description of 'sink.bulk-flush.max-actions'

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

Flink Jira Bot updated FLINK-20979:
-----------------------------------
    Labels: auto-deprioritized-major pull-request-available stale-minor starter  (was: auto-deprioritized-major pull-request-available starter)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Minor
>              Labels: auto-deprioritized-major, pull-request-available, stale-minor, 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.1#820001)