You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2026/09/10 07:38:00 UTC

[jira] [Resolved] (FLINK-40137) Extract ReaderRecoveryGate from DynamicKafkaSourceEnumerator

     [ https://issues.apache.org/jira/browse/FLINK-40137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martijn Visser resolved FLINK-40137.
------------------------------------
    Fix Version/s: kafka-5.1.0
       Resolution: Fixed

Fixed in apache/flink-connector-kafka:main 91e01a56ef6f5ea216a24c854a5a218616613f0b

> Extract ReaderRecoveryGate from DynamicKafkaSourceEnumerator
> ------------------------------------------------------------
>
>                 Key: FLINK-40137
>                 URL: https://issues.apache.org/jira/browse/FLINK-40137
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kafka
>            Reporter: Sylwester Lachiewicz
>            Assignee: Sylwester Lachiewicz
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: kafka-5.1.0
>
>
> The enumerator accumulated three interacting pieces of recovery-gating state (initial registration pending, reported splits pending redistribution, deferred metadata-update readers) inline, making the gating semantics hard to follow and untestable without a full container-based test setup. Extract this state and its logic into a dedicated ReaderRecoveryGate class with its own unit tests. No behavior change.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)