laughingman7743 commented on PR #156: URL: https://github.com/apache/flink-connector-jdbc/pull/156#issuecomment-4779008492
Follow-up on the root cause above: I filed [FLINK-39975](https://issues.apache.org/jira/browse/FLINK-39975) and opened https://github.com/apache/flink-connector-jdbc/pull/200 to fix the flaky `DerbyDynamicTableSourceITCase.testLimit`. The fix makes `JdbcSourceSplitReader` recover from a connection that is closed while opening a split during source cancellation: it re-establishes the connection and retries the split-open (bounded, mirroring the retry/reconnect handling in `JdbcOutputFormat.flush()`). It is non-masking — a genuine query error on a healthy connection is rethrown immediately, and an unreachable database still fails the job after the retry budget. A deterministic regression test reproduces the exact `08003 "No current connection"` error (the test fails without the fix and passes with it). Once #200 lands on `main`, this flaky test should stop reddening unrelated PRs (including this one). -- 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]
