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 2024/01/18 12:00:03 UTC

[jira] [Updated] (FLINK-34149) Flink Kafka connector can't compile against 1.19-SNAPSHOT

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

Martijn Visser updated FLINK-34149:
-----------------------------------
    Fix Version/s: 1.19.0

> Flink Kafka connector can't compile against 1.19-SNAPSHOT
> ---------------------------------------------------------
>
>                 Key: FLINK-34149
>                 URL: https://issues.apache.org/jira/browse/FLINK-34149
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka, Runtime / Checkpointing
>    Affects Versions: 1.19.0
>            Reporter: Martijn Visser
>            Priority: Blocker
>             Fix For: 1.19.0
>
>
> The Flink Kafka connector for {{main}} fails for 1.19-SNAPSHOT, see https://github.com/apache/flink-connector-kafka/actions/runs/7569481434/job/20612876543#step:14:134
> {code:java}
> Error:  COMPILATION ERROR : 
> [INFO] -------------------------------------------------------------
> Error:  /home/runner/work/flink-connector-kafka/flink-connector-kafka/flink-connector-kafka/src/main/java/org/apache/flink/connector/kafka/dynamic/source/enumerator/StoppableKafkaEnumContextProxy.java:[65,8] org.apache.flink.connector.kafka.dynamic.source.enumerator.StoppableKafkaEnumContextProxy is not abstract and does not override abstract method setIsProcessingBacklog(boolean) in org.apache.flink.api.connector.source.SplitEnumeratorContext
> {code}
> This interface seems to be added as part of https://issues.apache.org/jira/browse/FLINK-32514 / https://cwiki.apache.org/confluence/display/FLINK/FLIP-309%3A+Support+using+larger+checkpointing+interval+when+source+is+processing+backlog
> The FLIP indicates that the changes should be backward compatible, but that appears to have not been the case



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