[Snyk] Fix for 1 vulnerabilities

[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	com.fasterxml.jackson.dataformat:jackson-dataformat-csv: 2.16.2 -> 2.18.6 org.apache.kafka:connect-json: 3.9.1 -> 4.0.0 org.apache.kafka:connect-runtime: 3.9.1 -> 4.0.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:

🦉 Allocation of Resources Without Limits or Throttling

[d4v1de]

This set of upgrades includes a major, high-risk update to Apache Kafka components and a low-risk minor update for Jackson CSV.

High Risk: org.apache.kafka:connect-json & connect-runtime (3.9.1 → 4.0.0)

This major version upgrade introduces significant breaking changes that require environment and configuration updates before deployment.

Key Breaking Changes:

• ZooKeeper Removed: Kafka 4.0.0 completely removes support for ZooKeeper, making KRaft (Kafka Raft) the only mode for metadata management. Clusters must be migrated to KRaft before upgrading to version 4.0.0.
• Java 17 Required: Kafka Connect and its tools now require Java 17 to run. Kafka Clients and Streams require Java 11.
• Client Protocol Incompatibility: Support for legacy client protocols has been removed. Brokers running version 4.0 will not accept connections from clients older than version 2.1.
• Logging Framework Change: The logging system has been migrated from Log4j to Log4j2. Existing Log4j configurations must be converted.

Recommendation: Do not merge this upgrade without a comprehensive migration plan. The environment must be upgraded to Java 17, and the Kafka cluster must be migrated from ZooKeeper to KRaft mode prior to this upgrade.

Low Risk: com.fasterxml.jackson.dataformat:jackson-dataformat-csv (2.16.2 → 2.18.6)

This is a minor version upgrade that includes bug fixes, performance improvements, and new features without introducing breaking changes. No platform requirement changes, such as for the JDK, were noted in the release documentation. This upgrade is considered safe.

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