201811510411lw commented on PR #12366: URL: https://github.com/apache/seatunnel/pull/12366#issuecomment-6282689288
Thanks for the CI rerun. I downloaded the four unit-test report artifacts from [Build run #25](https://github.com/201811510411lw/seatunnel/actions/runs/39233668483). All four jobs (JDK 11/17 on Ubuntu/Windows) fail in the same test: ```text org.apache.seatunnel.connectors.seatunnel.jdbc.JdbcOptionRuleCompletenessTest Connector 'Jdbc' has unknown option keys: [numeric_special_value_as_null] ``` This comes from the latest `dev` content merged into this branch: [#12792](https://github.com/apache/seatunnel/commit/d99736ffb355a06dc38b41f20b3f357bde5e3412) adds `numeric_special_value_as_null` to the common JDBC options and the source rule, while the JDBC sink rule does not declare it. The completeness test from [#12800](https://github.com/apache/seatunnel/commit/5734e4feb583cf8d0d1d2b4e1fd5129b32a1a3d8) then reports it as an unknown sink option. The failure is reproducible across all four environments and is outside this PR's touched code: the Paimon routing and Flink sink changes are unrelated to JDBC. The focused Paimon routing tests remain green locally. Could this upstream JDBC issue be fixed on `dev` first? Once the fix lands, I can sync the branch and rerun CI. -- 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]
