oscerd opened a new issue, #1778: URL: https://github.com/apache/camel-kafka-connector/issues/1778
## Motivation Apache Kafka 4.x has been GA since early 2025, and the latest bugfix release is **4.2.1** (May 30, 2026). The camel-kafka-connector project currently depends on Kafka **3.9.2**, which is the last release in the 3.x line. Kafka 4.x brings significant changes that the project should adopt: - **ZooKeeper removal** — Kafka 4.0 removed ZooKeeper entirely in favor of KRaft mode. Continuing to depend on 3.x ties the project to a legacy architecture. - **Scala 2.12 dropped** — Only Scala 2.13 is supported starting with Kafka 4.0. The `kafka_2.12` Maven artifact no longer exists. - **Java 17 required** — Kafka Connect and brokers now require Java 17 (the project already targets Java 17, so this is a no-op). - **Security and stability** — Kafka 4.2.1 includes cumulative bugfixes and security improvements from 4.0 through 4.2. ## Scope of changes 1. **Version bump**: `kafka.version` from `3.9.2` to `4.2.1` 2. **Scala migration**: `kafka_2.12` artifacts → `kafka_2.13`, Scala library `2.12.12` → `2.13.17` 3. **Dependency alignment**: Add `connect-json` to `<dependencyManagement>` to prevent transitive version mismatch from `apicurio-registry-utils-converter` (which pulls `connect-json:3.6.1`) 4. **Test container images**: Update Strimzi images from `0.32.0-kafka-3.2.1` to `0.51.0-kafka-4.2.0` 5. **Cleanup**: Remove ZooKeeper logger configuration from test `log4j2.properties` ## Compatibility The Kafka Connect public APIs (`connect-api`, `connect-runtime`, `connect-transforms`, `kafka-clients`) are backward-compatible across this version range. No source code changes are required in the core module or connector implementations. ## Testing - All 101 core unit tests pass - Integration tests (timer, file, http, https, syslog, netty, netty-http, ssh, jdbc) all pass against Kafka 4.2.1 -- 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]
