DanielLeens opened a new pull request, #11426: URL: https://github.com/apache/seatunnel/pull/11426
## Purpose The Kafka restore start-mode E2E cases reused fixed topics and consumer groups across template invocations. Retained records and committed offsets could therefore leak between runs and make the restore assertions flaky or falsely successful. ## Changes - Isolate source topics, sink topics, and consumer groups for earliest, latest, and timestamp restore cases. - Recreate the fixed source topic required by the `specific_offsets` map key while isolating its sink topic and consumer group. - Use the active dynamic consumer group when moving the external offset beyond the savepoint position. - Validate savepoint, submit, restore, and cancel command results, and join the asynchronous streaming commands with bounded waits. ## Validation - `spotless:apply` for `connector-kafka-e2e` - `verify -DskipTests` for `connector-kafka-e2e` (includes test compilation and Spotless check) - Two independent code reviews passed with no blocking findings Docker/Testcontainers E2E was not run locally. GitHub CI will exercise the real Kafka savepoint and restore lifecycle. `seatunnel-engine-ui` was excluded because this change does not touch the UI. -- 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]
