DanielLeens opened a new pull request, #11190: URL: https://github.com/apache/seatunnel/pull/11190
## Summary - avoid using `Connection.isValid(timeout)` for Xugu pooled connections - configure the JDBC sink pool to use a Xugu-compatible validation query - add regression tests for the validation fallback and pool configuration ## Root cause `JdbcXuguIT` fails in shared CI because the Xugu driver throws from `Connection.isValid(timeout)`, which is used by the pooled JDBC path during writer initialization. ## Validation - `./mvnw -nsu -Dmaven.gitcommitid.skip=true -pl seatunnel-connectors-v2/connector-jdbc -am spotless:apply` - `./mvnw -nsu -Dmaven.gitcommitid.skip=true -pl seatunnel-connectors-v2/connector-jdbc -am -DskipTests -DskipITs -DskipUTs package -Dspotless.skip=true -Dcheckstyle.skip=true` - `./mvnw -nsu -Dmaven.gitcommitid.skip=true -pl seatunnel-connectors-v2/connector-jdbc -am -DskipTests -DskipITs -DskipUTs install -Dspotless.skip=true -Dcheckstyle.skip=true` - `./mvnw -nsu -Dmaven.gitcommitid.skip=true -pl seatunnel-connectors-v2/connector-jdbc -DskipITs -DfailIfNoTests=false -Dtest=JdbcConnectionValidationUtilsTest,JdbcSinkWriterTest test -Dspotless.skip=true -Dcheckstyle.skip=true` ## Notes - `seatunnel-engine-ui` was not built because this change only touches `connector-jdbc`. - Docker is not available in this environment, so the Xugu integration test path was not rerun locally. -- 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]
