DanielLeens opened a new pull request, #11205: URL: https://github.com/apache/seatunnel/pull/11205
## What does this PR change? This stabilizes the Kafka exactly-once E2E verification helper used by `KafkaIT`. The failing CI path was reading sink records by assuming that `expectedCount` committed records must occupy the contiguous offset range `[startOffset, startOffset + expectedCount)`. That assumption is wrong for `read_committed`: aborted transactional offsets can be skipped, so the next visible committed records may span a wider offset range. This PR changes the helper to: - snapshot the current visible end offset for the `READ_COMMITTED` consumer - consume records from `startOffset` until that visible end offset - keep the test assertion strict on the final visible record count and values ## Why is this needed? `#11183` exposed a shared failure in: - `KafkaIT.testKafkaToKafkaExactlyOnceOnStreaming` That failure is unrelated to the dead-link Node 22 change itself and can block unrelated PRs. ## How was this verified? - `JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home ./mvnw spotless:apply -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-kafka-e2e -nsu -Dmaven.gitcommitid.skip=true -T 3C` - `JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home ./mvnw -q -DskipTests verify -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-kafka-e2e -nsu -Dmaven.gitcommitid.skip=true -T 3C` I could not run the Testcontainers E2E locally in this worktree because the local Docker daemon was unavailable (`Cannot connect to the Docker daemon at unix:///Users/stone/.docker/run/docker.sock`). -- 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]
