[Snyk] Security upgrade org.apache.kafka:connect-json from 3.9.1 to 4.0.2

[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
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-15365924	828	org.apache.kafka:connect-json: 3.9.1 -> 4.0.2 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:

🦉 Allocation of Resources Without Limits or Throttling

[d4v1de]

This major version upgrade to Apache Kafka 4.0.x introduces significant and mandatory architectural changes that require careful planning and environment updates before upgrading.

Key Breaking Changes:

• ZooKeeper Removed: The most critical change in Kafka 4.0 is the complete removal of ZooKeeper. Kafka clusters must now run in KRaft (Kafka Raft) mode. Before upgrading this connector, your entire Kafka cluster must be migrated from ZooKeeper to KRaft mode. This is a complex, mandatory infrastructure migration.

• Java 17 Required: Kafka Connect 4.0 (and brokers/tools) now requires Java 17 to run. The environment running the Kafka Connect workers must be upgraded to Java 17.

• API and Dependency Changes: Many APIs deprecated in previous versions have been removed. Additionally, some transitive dependencies may have been removed; projects that relied on connect-json being included via another library (like Kafka Streams) may now need to declare the dependency explicitly in their build configuration.

Recommendation: Do not merge this upgrade without a comprehensive migration plan. The Kafka cluster must first be successfully migrated to KRaft mode, and the Connect worker environment must be upgraded to Java 17. Due to the scale of these prerequisite changes, this upgrade should be handled as a major project.

Source: Apache Kafka 4.0 Release Announcement, Upgrade Guide

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