You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2025/06/17 14:12:00 UTC

[jira] [Resolved] (NIFI-14630) Correct usage of KafkaClientComponent interface

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

David Handermann resolved NIFI-14630.
-------------------------------------
    Fix Version/s: 2.5.0
       Resolution: Fixed

> Correct usage of KafkaClientComponent interface
> -----------------------------------------------
>
>                 Key: NIFI-14630
>                 URL: https://issues.apache.org/jira/browse/NIFI-14630
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Peter Turcsanyi
>            Assignee: Peter Turcsanyi
>            Priority: Minor
>             Fix For: 2.5.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> KafkaClientComponent interface defines component properties for configuring the Kafka connection (Bootstrap Servers, Security Protocol, etc.).
> Historically, the Kafka processors implemented this interface and used the properties.
> After the Kafka 3 redesign, the processors do not handle the Kafka connection anymore but PublishKafka still implements KafkaClientComponent without using the properties.
> On the hand, Kafka3ConnectionService duplicates the properties instead of implementing the interface (or using it as a static constant interface).
> Correct the interface usage: remove from PublishKafka, add in Kafka3ConnectionService.



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