[Snyk] Security upgrade com.datastax.oss:stream-storage-server from 4.14.7.1.0.4 to 4.16.7.0.0.0

[pushkala-datastax]

Snyk has created this PR to fix 2 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-IONETTY-18170202	710	com.datastax.oss:stream-storage-server: 4.14.7.1.0.4 -> 4.16.7.0.0.0 No Path Found Proof of Concept
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-IONETTY-18170204	710	com.datastax.oss:stream-storage-server: 4.14.7.1.0.4 -> 4.16.7.0.0.0 No Path Found 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

[pushkala-datastax]

This is an upgrade of a server-side component within the DataStax streaming ecosystem, likely related to Apache Pulsar and BookKeeper. The version moves from 4.14.x to 4.16.x.

Official, detailed release notes for this specific component and version range were not found. Without a changelog, it is impossible to confirm the absence of breaking changes to APIs, configuration, or storage formats.

Recommendation: Due to the lack of documentation, this upgrade carries uncertainty. It is recommended that teams relying on DataStax streaming products (like Luna or Astra Streaming) review their internal documentation or contact support for details on this version jump. Thorough testing in a staging environment is critical to validate compatibility and behavior before deploying to production.

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