[
https://issues.apache.org/jira/browse/NIFI-14482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945123#comment-17945123
]
David Handermann commented on NIFI-14482:
-----------------------------------------
Thanks [~pvillard] and [~joewitt].
Although I agree the component naming is a bit awkward under the circumstances,
perhaps it is reasonable to view it as a minimum version for expected
compatibility. Although the Kafka 4 release notes indicate that it is
compatible for Kafka 2.1 brokers, certain features like KRaft require 3.3 or
higher.
All that to say, I agree with a simple dependency upgrade for now, and it might
be worth noting a minimum expected broker version.
> Bump Kafka components to Kafka 4 client
> ---------------------------------------
>
> Key: NIFI-14482
> URL: https://issues.apache.org/jira/browse/NIFI-14482
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> Kafka 4 has been released and, since the refactor done in NIFI-14375, there
> is no breaking change at the client level to go with Kafka 4. We currently
> have a specific controller service that is named after Kafka 3, however,
> given that there is no breaking change, I think it is better to just bump the
> version in the existing controller service rather than creating a new
> implementation with no code change and expect NiFi users to switch from one
> controller service to another.
> [https://kafka.apache.org/blog#apache_kafka_400_release_announcement]
> [https://kafka.apache.org/documentation/#upgrade_4_0_0]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
