DanielLeens commented on issue #11769: URL: https://github.com/apache/seatunnel/issues/11769#issuecomment-5395002685
Thanks for rechecking this against the newer patch set. That result is important: it confirms this issue is not fully covered by #9942 or #10793, so there is still an open functional gap on current `dev`. The issue should stay open for the current repair path: 1. #11879 keeps the regression test for the multi-table replay path; 2. #11883 is the active functional-fix candidate for the MySQL sink connection leak / stale-statement behavior. @zhang-arvin, please keep the fix scoped to the reproduce path discussed here and continue linking the exact failing/recovered path back to this issue as the PR evolves. @NaughtyYang, if possible, please add the exact `dev` commit or build you retested, plus the relevant failing log snippet around the `08S01` and replay step. That will help us compare the remaining runtime gap directly against the current PR behavior. -- 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]
