zhangshenghang opened a new issue, #12419: URL: https://github.com/apache/seatunnel/issues/12419
## Problem Cancelling a SeaTunnel Zeta job interrupts the task thread, but the JDBC source does not actively cancel the currently executing JDBC statement. If a JDBC driver blocks in executeQuery or ResultSet.next, the task cleanup and JDBC connection close can be delayed. ## Impact Long-running JDBC source queries may continue running after a user cancels the job, and the source connection may remain open until the JDBC call returns or the driver-specific timeout is reached. ## Expected behavior When a running job is cancelled, the JDBC source should actively cancel the current Statement, close the associated JDBC resources, and then complete the normal task cancellation lifecycle. ## Scope This issue covers a generic JDBC Source cancellation hook and a reproducible end-to-end test for an in-flight JDBC query. Database-specific driver behavior may still require vendor-specific validation. -- 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]
