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

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/02/09 06:52:00 UTC

[jira] [Resolved] (CAMEL-16138) Allow KafkaClientFactory to be used without explicit broker URLs

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

Claus Ibsen resolved CAMEL-16138.
---------------------------------
    Fix Version/s:     (was: 3.9.0)
                   3.8.0
       Resolution: Fixed

The check is now moved to the client factory, so a custom impl can do its own, and for example return null in broker urls. Then they are not set on the kafka props.

> Allow KafkaClientFactory to be used without explicit broker URLs
> ----------------------------------------------------------------
>
>                 Key: CAMEL-16138
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16138
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-kafka
>            Reporter: Nicola Ferraro
>            Assignee: John Poth
>            Priority: Major
>             Fix For: 3.8.0
>
>
> CAMEL-16071 has added support for KafkaClientFactory (thanks to [~javierholguera]). It allows plugging a different implementation of the Kafka Producer/Consumer, but the component still requires setting the "brokers" configuration property in the component/endpoint, otherwise an IllegalArgumentException is thrown.
>  
> This prevents users and platforms to plug implementations of the Kafka Producers/Consumers with fully externalized configuration (e.g. in Camel-Quarkus we may be able in the near future to plug configuration injected into files via Kubernetes service-binding).
>  
> I think the check on the presence of the "brokers" property should be moved into the default factory.
>  
> cc: [~jpoth]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)