DanielCarter-stack commented on issue #10632:
URL: https://github.com/apache/seatunnel/issues/10632#issuecomment-4099972128

   <!-- code-pr-reviewer -->
   Thanks for proposing this Debezium update. After analyzing the codebase, I 
have some concerns about the upgrade scope.
   
   **Current Version Locations:**
   - `seatunnel-connectors-v2/connector-cdc/pom.xml:44`
   - `seatunnel-formats/seatunnel-format-compatible-debezium-json/pom.xml:29`
   - `seatunnel-connectors-v2/connector-kafka/pom.xml:34`
   
   **Risk Assessment:**
   The Oracle CDC connector uses Debezium internal APIs (e.g., 
`io.debezium.connector.oracle.logminer.*`), which are likely incompatible 
across major versions and will require significant refactoring.
   
   **Recommendation:**
   Consider a staged upgrade to reduce risk:
   1. Upgrade to Debezium 2.x LTS first (e.g., 2.5 or 2.6)
   2. Validate all CDC connectors (MySQL/PostgreSQL first, Oracle last)
   3. Then consider 3.x after 2.x is stable
   
   Jumping from 1.9.8 directly to 3.4.2 is a large span—a phased approach would 
be safer.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to