dybyte opened a new pull request, #9942: URL: https://github.com/apache/seatunnel/pull/9942
Fixes: https://github.com/apache/seatunnel/issues/9886 ### Purpose of this pull request This PR ignores `JdbcConnectorException` thrown during remaining batch execution in `closeStatements()` and logs the error instead of propagating the exception. When `executeBatch()` is called in `closeStatements()`, a `JdbcConnectorException` may occur if the statement is already closed. Ignoring this exception is preferable, as propagating it can cause confusion in upper layers. For more details, please refer to the related issue. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? No additional tests were added for this change. ### Check list * [ ] If any new Jar binary package adding in your PR, please add License Notice according [New License Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/contribution/new-license.md) * [ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs * [ ] If you are contributing the connector code, please check that the following files are updated: 1. Update [plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties) and add new connector information in it 2. Update the pom file of [seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml) 3. Add ci label in [label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml) 4. Add e2e testcase in [seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/) 5. Update connector [plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config) -- 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]
