[
https://issues.apache.org/jira/browse/KAFKA-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665261#comment-16665261
]
Allen Tang commented on KAFKA-6890:
-----------------------------------
I personally believe in exposing as much capability out of Kafka Connect as
possible and enabling users to tinker with whatever they choose to, but they
should exercise caution and be aware of the impact in full in doing so. As
such, I'd hate to see blacklisting of any client configs, especially
"consumer.bootstrap.servers" and "producer.bootstrap.servers"; I've been using
connector-level overrides for these two configs in our prod environment to
great effect to allow a single cluster of Kafka Connect to write/read data
across multiple Kafka clusters.
> Add connector level configurability for producer/consumer client configs
> ------------------------------------------------------------------------
>
> Key: KAFKA-6890
> URL: https://issues.apache.org/jira/browse/KAFKA-6890
> Project: Kafka
> Issue Type: New Feature
> Components: KafkaConnect
> Reporter: Allen Tang
> Priority: Minor
>
> Right now, each source connector and sink connector inherit their client
> configurations from the worker properties. Within the worker properties, all
> configurations that have a prefix of "producer." or "consumer." are applied
> to all source connectors and sink connectors respectively.
> We should also provide connector-level overrides whereby connector properties
> that are prefixed with "producer." and "consumer." are used to feed into the
> producer and consumer clients embedded within source and sink connectors
> respectively. The prefixes will be removed via a String#substring() call, and
> the remainder of the connector property key will be used as the client
> configuration key. The value is fed directly to the client as the
> configuration value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
