davidzollo commented on PR #11639:
URL: https://github.com/apache/seatunnel/pull/11639#issuecomment-5441876521

   Thanks @SEZ9 for the careful review and for keeping the migration boundary 
precise.
   
   This update is now rebased onto the current `dev` and marked ready for 
review. It addresses the documentation blockers in both language versions:
   
   - `connector-cdc-base` is now described accurately: it still ships five 
patched `io.debezium` classes. Four override stock `debezium-core` classes; 
`DefaultHeartbeatConnectionProvider` is SeaTunnel-only and has no stock class 
to filter.
   - The third-party migration note now requires declaring `debezium-api`, 
`debezium-embedded`, `zstd-jni`, and the connector-specific Debezium artifact. 
It also explains the required outer and nested-class shade exclusions, the need 
to restate them for a connector-owned shade filter, and the atomic 
plugin-upgrade requirement.
   - I added a regression guard that reads both actual `debezium-core` shade 
filters (`connector-cdc/pom.xml` and the openGauss override) and verifies they 
exactly cover the four stock overrides. It also verifies the fifth patched 
class is absent from the resolved stock Debezium core artifact.
   
   I also investigated the old red workflow: its failures were an unrelated 
Windows `seatunnel-api` test, a Docker Hub timeout pulling `mysql:8.0.43` for 
Oracle IT, and a Paimon shutdown timeout. The rebase and push have triggered a 
fresh current-head CI run; I will use that run as the merge signal rather than 
treating the older failures as a CDC regression.


-- 
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