spuru9 opened a new pull request, #338:
URL: https://github.com/apache/flink-connector-kafka/pull/338

   ## What is the purpose of the change
   
   Upgrade `kafka-clients` from 4.2.0 to 4.4.0.
   
   ## Brief change log
   
   - `kafka.version` 4.2.0 -> 4.4.0.
   - `FlinkKafkaInternalProducer#flushNewPartitions`: 
`TransactionalRequestResult#await()` was replaced by `await(long, TimeUnit, 
String)` in 4.3.0. Call it with `Long.MAX_VALUE` to keep the existing 
wait-forever behavior.
   - Pin `org.jetbrains:annotations` 24.1.0 in `dependencyManagement`: 
`kafka-clients` -> `zstd-jni` (24.1.0) and `testcontainers` -> `duct-tape` 
(17.0.0) no longer converge in the e2e module.
   
   Note: `await(long, TimeUnit, String)` does not exist before 4.3.0, so the 
connector no longer works with older `kafka-clients`.
   
   ## Verifying this change
   
   - `flink-connector-kafka` unit tests and ITCases: sink package 147, rest 
398, all pass except 
`KafkaWriterFaultToleranceITCase#testFlushExceptionWhenKafkaUnavailable`, which 
also fails intermittently on 4.2.0 (1 of 3 runs on each version).
   - `mvn validate -Pcheck-convergence` passes on all modules.
   - Not run: e2e tests.
   
   ## Does this pull request potentially affect one of the following parts:
   
   - Dependencies (does it add or upgrade a dependency): yes
   - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
   - The serializers: no
   - The runtime per-record code paths (performance sensitive): no
   - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no (touches the 
transaction flush path of the exactly-once sink)
   
   ##### Was generative AI tooling used to co-author this PR?
   - [X] Yes
   
   Generated-by: Claude Code (claude-sonnet-5-5)
   


-- 
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]

Reply via email to