davidzollo opened a new pull request, #11161: URL: https://github.com/apache/seatunnel/pull/11161
## Why - CI for PR #11137 is failing in `JdbcDb2UpsertIT.testDb2UpsertE2e` - the assertion reads `C_UPDATED_AT` without a deterministic row order, so the expected timestamp sequence can be compared against the wrong row order ## What - add `ORDER BY C_INT` to the DB2 verification queries in `JdbcDb2UpsertIT` - keep the original timestamp assertions unchanged and only stabilize the result ordering by the integer primary key ## Validation - `./mvnw spotless:apply` - `./mvnw -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-common,seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-part-1 -DskipTests test-compile` - attempted real E2E path with `./mvnw -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-common,seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-part-1 -Dtest=JdbcDb2UpsertIT -Dsurefire.failIfNoSpecifiedTests=false test` ## Validation notes - `seatunnel-engine-ui` was not built because this change only touches JDBC E2E tests - the local E2E reached the real DB2 container startup and test bootstrap, but the run is still blocked by missing prebuilt starter jars in the local environment, so full end-to-end completion could not be finished on this machine -- 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]
