SEPURI-SAI-KRISHNA commented on PR #12899:
URL: https://github.com/apache/seatunnel/pull/12899#issuecomment-6282253220
The `Build` check here is red, and none of it comes from this change.
Details so nobody has to re-derive them.
Fork run `39258348421` is 79 success, 11 skipped, 2 cancelled, 4 failure.
The four failures are exactly the four `unit-test` legs, `(11, ubuntu)`, `(17,
ubuntu)`, `(11, windows)` and `(17, windows)`.
All four die at the same place, in `connector-jdbc`, which this PR does not
touch:
```
JdbcOptionRuleCompletenessTest.testSinkRuleDeclaresAllSinkOptions
OptionValidationException: Connector 'Jdbc' has unknown option keys:
[numeric_special_value_as_null]
```
This is a pre-existing break on `dev`, already tracked as #12874 with the
fix in #12875. The mechanism is a timing collision between two merged PRs:
- #12800 (merged 2026-10-16 18:12Z) added `JdbcOptionRuleCompletenessTest`,
which reflects over `JdbcSinkOptions` and therefore over everything it inherits
from `JdbcCommonOptions`.
- #12792 (merged 2026-10-18 14:38Z) added `numeric_special_value_as_null` to
`JdbcCommonOptions` and declared it only in the source rule.
I checked this against the current `dev` head rather than a local copy:
`JdbcSinkFactory` references `NUMERIC_SPECIAL_VALUE_AS_NULL` zero times,
`JdbcConnectionConfig` reads it three times, and the guard test is present with
no exclusion. So `dev` has been red on `unit-test` since 2026-10-18 14:38Z.
Two further checks. I reproduced the same failure locally on a tree carrying
no JDBC changes. And my unrelated #12909, a `connector-file` change, fails the
identical step on all four legs, which is the control you would want before
blaming either diff.
What is green and relevant here: the reactor reaches `connector-jdbc` long
after `seatunnel-transforms-v2`, so the module this PR changes had already
built and run its own tests on the leg that is marked red.
No rerun can go green until #12875 merges, so I am leaving the badge as it
is rather than burning runner time. Once #12875 lands I will sync and rerun.
--
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]
