[Snyk] Security upgrade com.datastax.cassandra:cassandra-driver-core from 3.11.5 to 4.0.0

[Anurag-Sin]

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

Snyk changed the following file(s):

• cassandra-hadoop-util/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-15907551	125	com.datastax.cassandra:cassandra-driver-core: 3.11.5 -> 4.0.0 Major version upgrade No Path Found No Known Exploit

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

[Anurag-Sin]

This is a major version upgrade from 3.x to 4.x which is not binary compatible with previous versions and requires significant code refactoring. The driver has undergone a major redesign.

Key Breaking Changes:

• New Maven Coordinates: The package's groupId has changed from com.datastax.cassandra to com.datastax.oss. You must update your pom.xml or other build files.
• API Redesign: The Cluster and Session objects have been replaced by a unified CqlSession interface. All code creating and using sessions must be rewritten.
• Package and Import Changes: The Java package structure has been reorganized. For example, classes previously in com.datastax.driver.core are now in new locations, requiring updates to all import statements.
• Immutable Statements: Statement objects (e.g., BoundStatement) are now immutable. Methods that modify them, like setInt(), now return a new instance instead of modifying the object in place.
• Configuration Overhaul: Configuration has been completely refactored. It is now primarily file-based (application.conf) instead of programmatic using builder methods like .withLoadBalancingPolicy().
• Runtime Requirements: The driver now requires Java 8 or higher. Support for Cassandra protocol versions v1 and v2 has been dropped, making the driver compatible with Cassandra 2.1+ and DSE 4.7+.

Recommendation: This upgrade cannot be performed without significant developer effort. A dedicated migration plan is necessary to address the extensive API and configuration changes. Review the official upgrade guide thoroughly before proceeding.

Source: DataStax Java Driver 4.x Upgrade Guide

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