You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Marton Greber (Jira)" <ji...@apache.org> on 2026/04/01 08:43:00 UTC

[jira] [Created] (FLINK-39374) Rename KuduWriterConfig.maxBufferSize to maxMutationBufferOps

Marton Greber created FLINK-39374:
-------------------------------------

             Summary: Rename KuduWriterConfig.maxBufferSize to maxMutationBufferOps
                 Key: FLINK-39374
                 URL: https://issues.apache.org/jira/browse/FLINK-39374
             Project: Flink
          Issue Type: Bug
          Components: Connectors / Kudu
            Reporter: Marton Greber


KuduWriterConfig.Builder exposes a field named maxBufferSize, but it maps to KuduSession.setMutationBufferSpace() — a count of buffered mutation operations, not a byte size. The name maxBufferSize implies a byte quantity.

The field, its getter/setter, and the corresponding CLI option (sink.max-buffer-size) should be renamed to reflect the actual semantics (e.g. maxMutationBufferOps / sink.max-mutation-buffer-ops).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)