[
https://issues.apache.org/jira/browse/FLINK-36648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939240#comment-17939240
]
Thomas Cooper edited comment on FLINK-36648 at 3/28/25 4:23 PM:
----------------------------------------------------------------
[~kunni] now that the Flink 2.0.0
[PR|https://github.com/apache/flink-connector-kafka/pull/140] is merged, I have
updated my Kafka 3.9.0
[PR|https://github.com/apache/flink-connector-kafka/pull/138] and that passes
all the tests locally.
However, do we actually want to have Kafka 4.0.0 clients in the Connector 4.0
release?
I have created an issue
([FLINK-37583|https://issues.apache.org/jira/browse/FLINK-37583]) for the Kafka
4.0.0 update. As mentioned there, updating to the 4.0.0 clients will mean the
connector can no longer talk to brokers running Kafka 2.0 or older. Given that,
I think it makes sense to move to the 4.0.0 client as part of the
flink-connector-kafka 4.0 release. The major version increase can indicate that
there is a removal of support for older brokers.
was (Author: tomncooper):
[~kunni] now that the Flink 2.0.0
[PR|https://github.com/apache/flink-connector-kafka/pull/140] is merged, I have
updated my Kafka 3.9.0
[PR|https://github.com/apache/flink-connector-kafka/pull/138] and that passes
all the tests locally.
However, do we actually want to have Kafka 4.0.0 clients in the Connector 4.0
release?
> Release flink-connector-kafka v4.0.0 for Flink 2.0
> --------------------------------------------------
>
> Key: FLINK-36648
> URL: https://issues.apache.org/jira/browse/FLINK-36648
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Kafka
> Affects Versions: kafka-3.4.0
> Reporter: Yanquan Lv
> Assignee: Yanquan Lv
> Priority: Major
> Labels: pull-request-available
> Fix For: kafka-4.0.0
>
>
> Flink now already have a release for 2.0-preview1 version, Kafka, as one of
> the most commonly used connectors, needs to be bump to this version as soon
> as possible for users and developers to use.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
