[Snyk] Security upgrade io.debezium:debezium-connector-oracle from 2.6.1.Final to 3.0.0.Final

[pushkala-datastax]

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-18517159	710	io.debezium:debezium-connector-oracle: 2.6.1.Final -> 3.0.0.Final Major version upgrade 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 major version upgrade from Debezium 2.x to 3.x introduces significant breaking changes that require both environment and configuration updates.

Key Breaking Changes:

• Java 17 Requirement: Debezium 3.0 and later now require a Java 17 runtime environment. This is an upgrade from previous versions that supported Java 11.
• New Default Log Mining Strategy for Oracle: The Oracle connector's default log mining strategy (database.log.mining.strategy) has been changed to online_catalog. Users who relied on the previous default will need to review their configuration to ensure the new strategy is appropriate for their environment or explicitly set the property to its former value.
• Removal of Deprecated Oracle Properties: Several configuration properties for the Oracle connector that were marked as deprecated in earlier versions have been completely removed. You must review your connector configuration and remove any of these deprecated properties to avoid startup failures.
• Removal of additional-condition Signal Field: For users of incremental snapshots via signaling, the deprecated additional-condition field has been removed.

Recommendation:
Before upgrading, verify that your runtime environment is Java 17. Carefully review your Oracle connector configuration to adapt to the new default mining strategy and remove any deprecated properties. Thorough testing is recommended after the upgrade to ensure the connector operates as expected.

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