DanielLeens commented on issue #10512: URL: https://github.com/apache/seatunnel/issues/10512#issuecomment-5111115900
Thanks for the detailed Oracle reproduction and for adding the table DDL / UPDATE example. I rechecked the current `dev` dependency state. The CDC modules, including `connector-cdc-oracle`, still use Debezium `1.9.8.Final`, so SeaTunnel has not yet picked up the later Debezium Oracle LOB fixes you pointed to. With `debezium.lob.enabled=true`, the behavior you described is therefore a real Oracle CDC LOB support gap, not just a bad SeaTunnel job option. At the same time, this should not be treated as a one-line Oracle connector change. A Debezium upgrade affects the shared CDC dependency surface across Oracle, MySQL, PostgreSQL, SQL Server, MongoDB, Vitess, and the common Debezium adapter code. The safe repair path is a focused PR that includes: 1. a Debezium upgrade compatibility audit for all CDC modules; 2. an Oracle CDC regression where a table has CLOB columns and an UPDATE changes only one CLOB / non-CLOB field while other LOB fields remain unchanged; 3. proof that the emitted row no longer contains `__debezium_unavailable_value` for unchanged LOB fields; 4. release-note or documentation wording if the fix only lands in `dev` / a future release line and is not backported to 2.3.12. One extra note: the issue body contains encoded connection credentials. Even if they were only test values, please rotate them if they came from a real environment, and avoid posting credentials in public issues in future reports. -- 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]
