yzeng1618 commented on PR #11971:
URL: https://github.com/apache/seatunnel/pull/11971#issuecomment-5707921389

   ### CI failure note: unrelated OpenGauss CDC regression on `dev`
   
   The current `updated-modules-integration-test-part-4` failures are not 
caused by this PR's JDBC query-only metadata changes. Both JDK legs fail in the 
existing `OpengaussCDCIT#testAddFieldWithRestore` test with the same assertion:
   
   ```text
   actual iterable was <null> at index [1][4]
   ```
   
   Failed jobs:
   - JDK 8: 
https://github.com/yzeng1618/seatunnel-dev/actions/runs/35062794202/job/104790155477
   - JDK 11: 
https://github.com/yzeng1618/seatunnel-dev/actions/runs/35062794202/job/104790155543
   
   The job log confirms that the live five-column schema is replaced by the 
four-column checkpoint schema during restore:
   
   ```text
   restore before: ROW<id INT,f_bytea BYTES,f_small SMALLINT,f_int INT,f_big 
BIGINT>
   restore after:  ROW<id INT,f_bytea BYTES,f_small SMALLINT,f_int INT>
   ```
   
   The first restored CDC record still contains `f_big=2147483647`, but 
`RestoreTableSchemaEvent` rebuilds the JDBC writer with a four-column INSERT, 
leaving the sink's `f_big` value as `NULL`.
   
   This is tracked as a `dev` baseline regression in #12344. That issue reports 
the same failure in unrelated Zeta PRs #12298 and #12299, reproducing 40/40 
times across two base commits and both JDK 8 and JDK 11. This PR does not 
modify OpenGauss CDC, the CDC restore path, or `AbstractJdbcSinkWriter`.
   
   Existing fixes are being discussed in #12321 and #12346. In particular, 
#12346's corresponding part-4 jobs have already passed on both JDK 8 and JDK 
11. To keep #11971 focused, I do not plan to mix the unrelated CDC fix into 
this PR. Once the upstream fix is merged into `dev`, I will sync the branch and 
rerun the failed checks.


-- 
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]

Reply via email to