DanielLeens commented on PR #11206: URL: https://github.com/apache/seatunnel/pull/11206#issuecomment-5381413688
I pushed `0bc52ddf500` to the current PR head. The failure was coming from the wildcard newly-added-table E2E using the fixed runtime table name `payments` / `source_payments`. In the failed run on August 20, 2026, the job submission path already saw `source.payments` before the runtime-create step, and the JDBC save-mode logs treated `sink.source_payments` as an existing table, which means this test was colliding with leaked state from another invocation instead of proving the newly-added-table path. This update keeps the production code unchanged and isolates the test by generating a unique runtime wildcard table name for each invocation, then deriving the matching sink table name from that value. That keeps the assertion focused on a table that definitely did not exist when the job started. Local proof in this branch is limited to formatting only, per the current SeaTunnel PR workflow: - `./mvnw spotless:apply -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-mysql-e2e -am -nsu` -- 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]
