qiuyanjun888 opened a new pull request, #22: URL: https://github.com/apache/flink-connector-kudu/pull/22
## Summary - Rename the Kudu writer buffer configuration from `maxBufferSize` to `maxMutationBufferOps`. - Add the new table option `sink.max-mutation-buffer-ops`. - Preserve backward compatibility for the old Java API and the deprecated `sink.max-buffer-size` option. ## Root Cause `KuduWriterConfig.maxBufferSize` and the table option `sink.max-buffer-size` describe the number of buffered mutation operations, not a byte size. This made the option name misleading compared with the underlying Kudu session setting. ## Changes - Add `KuduWriterConfig#getMaxMutationBufferOps()` and `Builder#setMaxMutationBufferOps(int)`. - Keep deprecated `getMaxBufferSize()` and `setMaxBufferSize(int)` delegating to the new API. - Add `KuduDynamicTableOptions.MAX_MUTATION_BUFFER_OPS` for `sink.max-mutation-buffer-ops` with `sink.max-buffer-size` as a deprecated key. - Update factory/writer wiring and existing Kudu table tests to use the new name. - Add focused tests for both the new option/API and deprecated compatibility paths. ## Validation - `mvn -pl flink-connector-kudu -Dtest=KuduWriterConfigTest,KuduDynamicTableFactoryOptionsTest -DfailIfNoTests=false test` - `mvn -pl flink-connector-kudu -DskipTests test` The Docker/Testcontainers-backed Kudu integration tests were not run locally because this environment does not provide a Docker socket. ## AI assistance disclosure This PR was prepared with AI assistance and manually validated with the commands above. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
