The GitHub Actions job "Flink Connector Kafka CI" on 
flink-connector-kafka.git/fix-topic-integrity-autocreate has failed.
Run started by GitHub user slachiewicz (triggered by slachiewicz).

Head commit for run:
ae51a1742fe0985a782a302afe8c3cb9584a31da / Sylwester Lachiewicz 
<[email protected]>
[FLINK-40622][Connectors/Kafka] Do not auto-create topics when checking topic 
integrity

A source that verifies topic integrity must not recreate the topic it is
verifying. Both the broker and the Kafka consumer allow topic
auto-creation by default, and the connector overrides neither, so after a
restart a restored reader polling its checkpointed partitions brought the
deleted topic back with a fresh id. The enumerator's check then reported
"was recreated" instead of "is missing".

That is what made SourceTopicIntegrityITCase.testTopicIntegrityFailure
flaky: whether the check or the readers got there first was a race, so it
only failed under load, and raising the wait in FLINK-40589 could not
help because the awaited message was never coming.

Default allow.auto.create.topics to false in KafkaSourceBuilder when the
integrity check is enabled. maybeOverride leaves an explicit user value
alone, so anyone who wants the Kafka default keeps it. Do not drop this
default: without it the flake returns and, worse, the connector silently
recreates a topic the user deleted.

Tests: KafkaSourceBuilderTest pins the default, the untouched
non-integrity case and the explicit-override case.
SourceTopicIntegrityITCase gains a reader-level test of the mechanism
that needs no savepoint race, plus a precondition guard so a lost race
fails where it happens instead of as a bare timeout.

Generated-by: Claude Code (Claude Opus 5)

Report URL: 
https://github.com/apache/flink-connector-kafka/actions/runs/34476732759

With regards,
GitHub Actions via GitBox

Reply via email to