li3zhi4 commented on PR #11618: URL: https://github.com/apache/seatunnel/pull/11618#issuecomment-5159362742
Good news: I've now **actually run the new e2e test locally** (with Docker) and it passes. **Result:** `MysqlCDCStopModeSpecificIT` → `Tests run: 1, Failures: 0, Errors: 0` ✅ (BUILD SUCCESS) What the test verifies end-to-end: 1. **Termination**: starts a MySQL CDC job with `startup.mode=specific` + `stop.mode=specific`, and asserts the job **terminates on its own (FINISHED)** at the configured binlog offset instead of running forever 2. **Data boundary**: rows written before the stop offset are synced; rows written after the stop offset are **not** synced (the test inserts them only after the snapshot phase completes, so only the binlog phase could pick them up — and it correctly stops at the stop offset) Two refinements made while running it locally (commits `de40a3d6f0` + `05f8a0702d`): - Test is restricted to the **Zeta engine** via `@DisabledOnContainer` (FLINK/SPARK don't support bounded incremental-split termination; same pattern as the existing `MysqlCDCSpecificStartingOffsetIT`) - The post-stop-offset rows are inserted only after the pre-stop rows are confirmed synced, fixing a timing issue where the snapshot phase read all rows Local environment note: I ran it with `-Dtestcontainer.version=1.21.4` (the repo's pinned 1.17.6 bundles an older docker-java that can't talk to Docker 29's API); CI uses the pinned version. Also merged the latest `dev` into the branch to keep it green. -- 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]
