DanielLeens commented on PR #12463: URL: https://github.com/apache/seatunnel/pull/12463#issuecomment-5882005088
Thanks for the update, and nice catch pulling in #12477! I re-checked the latest fork CI run at your rebased head (`4c80ec6`, run https://github.com/sun-9545sunoj/seatunnel/actions/runs/36453950596) job-by-job. Good news: the previous deterministic OceanBase CDC failure in `updated-modules-integration-test-part-6` (the `io.debezium.relational.TableId` `NotSerializableException`) is indeed gone now — the dev sync worked as expected. However, CI is not fully green yet: a new, unrelated failure showed up in `mysql-cdc-connector-it (11, ubuntu-latest)`: ``` [ERROR] Failed to execute goal on project connector-jdbc: Could not resolve dependencies for project org.apache.seatunnel:connector-jdbc:jar:3.0.0-SNAPSHOT: Failed to collect dependencies at org.apache.hive:hive-jdbc:jar:3.1.3 -> ... -> org.apache.hadoop:hadoop-hdfs:jar:2.7.1: Failed to read artifact descriptor for org.apache.hadoop:hadoop-hdfs:jar:2.7.1: Could not transfer artifact org.apache.hadoop:hadoop-hdfs:pom:2.7.1 from/to central (https://repo.maven.apache.org/maven2): transfer failed ..., status: 502 Bad Gateway ``` This is a transient Maven Central 502 while resolving `connector-jdbc`'s transitive Hive/Hadoop dependency chain — nothing to do with your chunk-splitter change. The strongest evidence: the identical `mysql-cdc-connector-it (8, ubuntu-latest)` leg in the very same run, resolving the exact same dependency tree, passed cleanly. No further rebase or code change needed on your side for this — I'd just re-run the failed `mysql-cdc-connector-it (11, ubuntu-latest)` job from your fork's Actions tab (a job-level rerun is enough; no need to re-run the whole workflow). My prior approval stands; there are no outstanding code-side blockers from my review. -- 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]
