DanielLeens commented on issue #11016: URL: https://github.com/apache/seatunnel/issues/11016#issuecomment-4640971697
I checked the behavior described here, and this does look like a real MySQL CDC schema-evolution bug rather than a configuration issue. The problematic path is the unqualified DDL resolution step. In a multi-database job where the same table name exists in more than one source database, the resolver should bind `ALTER TABLE products ...` to the database carried by the current CDC event. If it instead falls back to the first matched table name, schema isolation between `shop_a.products` and `shop_b.products` can break exactly in the way you described. Since you already prepared a candidate fix and regression coverage in PR #11015, this issue is in a good state for follow-up review rather than more reproduction work. I have labeled it as `bug`, and we can continue the implementation discussion on that PR. -- 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]
