JacobZheng0927 commented on PR #13139: URL: https://github.com/apache/seatunnel/pull/13139#issuecomment-6651603561
Additional real-environment validation completed on 2026-11-05 against an existing **StarRocks 3.4.1-2f78e09** deployment, separately from the StarRocks 2.2.1 Testcontainers run above. - Runtime: community SeaTunnel `3.1.0-SNAPSHOT`, Zeta local mode, Linux amd64, OpenJDK 11.0.32.1. A temporary Pod ran the community starter and connector artifacts on the same network as StarRocks. - Scenario: native StarRocks source (`BOOLEAN` column, declared SeaTunnel `TINYINT`) → JDBC sink → an actual `TINYINT` destination column. Source rows: `(1, false)`, `(2, true)`, `(3, NULL)`. - Controlled comparison: the same runtime, source data, configuration, and destination schema were used in both runs, with separate empty destination tables. Only the shared Arrow reader classes in the connector jars differed: compiled from base `a3743d7f52e9200a7733857ca813a0836bf66bba` versus PR head `36d95b320628bec6ce5379f1599033b38fc1dcb9` using the same compiler and dependencies. Jar entry comparison confirmed that only the reader and its synthetic enum-switch class changed. | Reader | Process exit | Result | | --- | --- | --- | | Before fix | 1 | JDBC field `flag` fails with `ClassCastException`; destination remains empty. | | After fix | 0 | Zeta job `FINISHED`; SQL readback matches exactly `(1, 0)`, `(2, 1)`, `(3, NULL)`, with no extra rows. | Relevant before-fix exception: ```text JdbcConnectorException: ErrorCode:[JDBC-10], ErrorDescription:[Data type cast failed] - error field:flag Caused by: java.lang.ClassCastException: class java.lang.Boolean cannot be cast to class java.lang.Byte ``` This also confirms that the failure occurs when the destination column is `TINYINT`; a `VARCHAR` destination is not required to trigger it. All three isolated test tables and the temporary Pod were removed after validation. No Flink/Spark validation is claimed. -- 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]
