DanielLeens opened a new pull request, #11181:
URL: https://github.com/apache/seatunnel/pull/11181
## What does this PR do?
Fixes a shared SAP HANA JDBC E2E failure that appears in unrelated PR CI
runs.
SAP HANA uses `TEST` as the target schema in this test setup, but the sink
configs only passed `database = "TEST"`. That left generated sink SQL and the
IT cleanup path without an explicit schema, which led to repeated `invalid
table name: ALLDATATYPES_SINK` failures.
This patch aligns the HANA IT baseline by:
- setting the HANA schema on `JdbcHanaIT`
- passing `schema = "TEST"` in both HANA sink configs that rely on generated
sink SQL
## How was this validated?
- `./mvnw -pl
seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-part-6
spotless:apply -DskipTests`
- `./mvnw -pl
seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-part-6
-DskipTests -Dskip.ui=true verify`
- attempted closer runtime validation with:
- `./mvnw -pl
seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-part-6
-Dskip.ui=true -Dtest=JdbcHanaIT#testJdbcDb -DfailIfNoTests=false test`
`seatunnel-engine-ui` was skipped because this fix only touches the JDBC
part-6 E2E module. The HANA IT start was blocked locally by an unresponsive
Docker socket: Testcontainers loaded `UnixSocketClientProviderStrategy` from
`~/.testcontainers.properties`, and direct `/_ping` against
`~/.docker/run/docker.sock` timed out.
--
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]
