DanielLeens opened a new pull request, #11179: URL: https://github.com/apache/seatunnel/pull/11179
## What does this PR do? This fixes the shared DM schema evolution E2E failure that has been showing up across unrelated PRs. The DM schema change configs were using `jdbc:dm://e2e_dmdb:5236` without the database segment, while the DM test setup and JDBC URL contract expect the database name to be present. That makes the JDBC source initialization fail with `OptionValidationException`, and the schema change jobs never reach the running state. This PR updates both DM schema evolution configs to use `jdbc:dm://e2e_dmdb:5236/SYSDBA` so they match the actual DM test environment. ## Validation - `./mvnw -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-ddl -am spotless:apply -DskipTests` - `./mvnw -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-ddl -am -DskipTests -Dskip.ui=true verify` Attempted closer runtime validation: - `./mvnw -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-ddl -Dskip.ui=true -Dtest=DmSchemaChangeIT -DfailIfNoTests=false verify` The targeted `DmSchemaChangeIT` run was started locally, but the local Docker environment stalled before test execution could proceed, and even `docker ps` stopped responding in the same window. The interrupted run ended before any test method executed (`Tests run: 0`). ## Notes - The reactor still passed through `seatunnel-engine-ui`, but frontend execution was skipped via `-Dskip.ui=true`. -- 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]
