[Snyk] Security upgrade org.apache.kafka:connect-runtime from 2.6.2 to 4.3.0

[d4v1de]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	HTTP Request Smuggling SNYK-JAVA-ORGECLIPSEJETTY-16061843	776	org.apache.kafka:connect-runtime: 2.6.2 -> 4.3.0 Major version upgrade Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[d4v1de]

This is a major version upgrade from 2.6.2 to a hypothetical 4.3.0, which crosses two major breaking release boundaries: 3.0.0 and 4.0.0. This upgrade requires significant developer action and careful planning.

Kafka 3.0.0 Breaking Changes:

• Default Producer Settings: The producer's default delivery guarantee is now stronger. acks is set to all and enable.idempotence is true by default. This may impact performance and requires verification.
• Java 8 Deprecated: Support for Java 8 is deprecated and will be removed in version 4.0.
• Kafka Connect: The internal converter properties (internal.key.converter, internal.value.converter) have been removed. Workers now default to JSONConverter. If you used a different internal converter, you must follow the migration steps in KIP-738.
• Configuration Removals: Several deprecated configurations have been removed, including rest.host.name, rest.port, port, host.name, advertised.port, and advertised.host.name. These must be replaced with the listeners configuration.
• Log4j Format Change: The default log4j log pattern for Connect workers now includes the connector context, which will change the format of your log lines.

Kafka 4.0.0 Breaking Changes:

• ZooKeeper Removed: Kafka 4.0.0 and later run in KRaft mode by default and do not support ZooKeeper. Clusters must be migrated to KRaft before upgrading to 4.0.
• Java 11/17 Required: Java 8 support is removed. Kafka Brokers, Connect, and Tools now require Java 17. Kafka Clients and Streams require Java 11.
• Message Formats v0 and v1 Dropped: Support for legacy message formats v0 and v1 is removed.

Recommendation: This upgrade cannot be performed directly. A multi-step migration is required. First, upgrade to a 3.x version while remaining on ZooKeeper. Then, migrate your cluster from ZooKeeper to KRaft mode. Finally, upgrade from your 3.x KRaft cluster to 4.x. Due to the complexity and multiple breaking changes, this upgrade should be handled as a separate, dedicated project.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.