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/03 12:07:01 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17277955#comment-17277955 ]
Claus Ibsen commented on CAMEL-16138:
-------------------------------------
btw we should focus on camel-vertx-kafka going forward. This component will become deprecated over time
> 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: Task
> Components: camel-kafka
> Reporter: Nicola Ferraro
> 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)