[
https://issues.apache.org/jira/browse/KAFKA-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-2798.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.9.0.0
Issue resolved by pull request 486
[https://github.com/apache/kafka/pull/486]
> Kafka Connect distributed configs can conflict with producer/consumer
> configs, making it impossible to control them independently
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-2798
> URL: https://issues.apache.org/jira/browse/KAFKA-2798
> Project: Kafka
> Issue Type: Bug
> Components: copycat
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
> Fix For: 0.9.0.0
>
>
> Right now we're using the approach to configs used by serializers where we
> just forward the configs for the entire worker to the producer and consumer.
> However, with the distributed mode, we now have a lot of conflicting configs
> because the distributed herder uses the group membership functionality and
> client networking libraries.
> We should instead use a sort of "namespaced" set of configs, which we already
> started doing with converters since we have multiple instances of converters
> instantiated by a single worker. We can use producer. and consumer. prefixes
> to isolate settings for the different components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
