You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jim Hughes (Jira)" <ji...@apache.org> on 2026/09/17 19:31:00 UTC
[jira] [Assigned] (FLINK-40703) Improve correctness coverage: Add ITCase for recovery from a checkpoint whose pooled transactional id was reused by a later checkpoint
[ https://issues.apache.org/jira/browse/FLINK-40703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Hughes reassigned FLINK-40703:
----------------------------------
Assignee: Aleksandr Savonin
> Improve correctness coverage: Add ITCase for recovery from a checkpoint whose pooled transactional id was reused by a later checkpoint
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-40703
> URL: https://issues.apache.org/jira/browse/FLINK-40703
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Reporter: Aleksandr Savonin
> Assignee: Aleksandr Savonin
> Priority: Major
>
> Motivation: improve end-to-end correctness coverage of the exactly-once sink.
> The POOLING recovery path is covered at writer level (ExactlyOnceKafkaWriterITCase) and unit level (KafkaCommitterTest, TransactionAbortStrategyImplTest, ProducerPoolImplITCase), but no test runs the real committer, the backchannel and a MiniCluster restore together.
> The KafkaSinkITCase recovery tests fail their jobs at checkpoint 2, so no third checkpoint ever reuses an id.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)