DanielLeens opened a new pull request, #11231: URL: https://github.com/apache/seatunnel/pull/11231
## Purpose - stabilize `KafkaIT.testKafkaToKafkaExactlyOnceOnStreaming` after the latest dev branch still failed in `kafka-connector-it` on the Flink 1.18 axis - make exactly-once test data production wait for Kafka broker acknowledgements instead of relying on fire-and-flush sends - surface producer-side send failures at the producer boundary instead of later as a misleading exactly-once sink count mismatch ## Root Cause - The failing CI run showed the Flink 1.18 variant reached healthy checkpoints up to checkpoint 58, but the assertion repeatedly saw only 9 expected records while keepalive records continued to arrive. - The test produced the initial records with `producer.send(record); producer.flush();` and never checked the returned Future, so a transient send failure after topic creation could be hidden and later appear as a sink-side exactly-once failure. ## Changes - Add `sendTextRecordAndWait` to synchronously wait for Kafka send acknowledgements. - Use it for exactly-once streaming, restore, batch seed records, and streaming keepalive records. ## Validation - `./mvnw -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-kafka-e2e spotless:apply -nsu -Dmaven.gitcommitid.skip=true` - `JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home ./mvnw -B -pl :connector-kafka-e2e -DskipTests -DskipITs=true -Dlicense.skipAddThirdParty=true -Dskip.ui=true -Dskip.spotless=true -Dmaven.gitcommitid.skip=true -nsu test-compile` ## Notes - Docker is not running on this local host, so the Testcontainers Kafka E2E case could not be rerun locally. - A full `-am test-compile` attempt is blocked by the existing fresh-worktree `seatunnel-config-shade` compile issue, unrelated to this Kafka test change. - `seatunnel-engine-ui` was not touched; no UI build was required. -- 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]
