DanielLeens commented on PR #10799: URL: https://github.com/apache/seatunnel/pull/10799#issuecomment-4881911936
Thanks for raising this. I rechecked the current staged head again against the actual CDC runtime path rather than only the high-level architectural claim. I do agree with the long-term direction in the concern: if SeaTunnel eventually wants true per-connector Debezium major-line independence, `connector-cdc-base` cannot remain the permanent version-lock point forever. On this exact unchanged head, though, Daniel's technical conclusion is still the same as before: this PR is currently a staged foundation step, not the final end-state proof of full multi-version isolation. The current revision still does not ship production `META-INF/services` adapter registrations that would put two real connector-owned Debezium lines into one user-reachable runtime path today. So I would still treat the remaining base-level Debezium coupling as a follow-up architectural hardening point, not as a new source blocker on this exact staged revision by itself. The practical next step for this PR is still the same: keep the scope narrow, sync with the latest `dev`, and rerun CI on the refreshed head. If a new code revision lands that changes the actual runtime boundary again, I am happy to do a fresh full re-review on top of that head. -- 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]
