goutamadwant commented on issue #10359: URL: https://github.com/apache/seatunnel/issues/10359#issuecomment-5446898531
@davidzollo @DanielLeens I check the latest dev and was checking the feasibility now. The feasibility has changed since the earlier discussion. Debezium now has an incubating Informix connector built on the IBM Change Streams API, so we would not need to implement a separate log parser. It supports initial snapshot and incremental streaming and looks like the most maintainable base for this connector. The blocker is version compatibility. SeaTunnel CDC currently uses Debezium 1.9.8 and targets Java 8. Informix support was introduced in Debezium 2.5, which requires Java 11. Adding only the Informix artifact would mix incompatible Debezium APIs and Java bytecode levels. I do not think backporting the connector or maintaining another Informix log reader would be a good long-term solution. Before starting implementation, can we agree on one of these directions: 1. Informix CDC waits for the SeaTunnel Debezium and Java baseline upgrade 2. Informix runs through an isolated Java 11+ connector runtime 3. the community prefers a custom IBM Change Streams adapter My preference is the first option, or the second if SeaTunnel wants an isolated runtime boundary. Once the direction is confirmed I can prepare a compatibility spike and define the source-only snapshot plus CDC MVP. Let me know. thanks! -- 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]
