Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Tue, 19 Dec 2017 22:57:00 +0000 (UTC)
From: "Randall Hauch (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.13126055.1513724170000.498023.1513724220037@Atlassian.JIRA>
In-Reply-To: <JIRA.13126055.1513724170000@Atlassian.JIRA>
References: <JIRA.13126055.1513724170000@Atlassian.JIRA> <JIRA.13126055.1513724170393@jira-lw-us.apache.org>
Subject: [jira] [Created] (KAFKA-6387) Worker's producer and consumer
 configs should inherit from worker configs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 19 Dec 2017 22:57:04 -0000

Randall Hauch created KAFKA-6387:
------------------------------------

             Summary: Worker's producer and consumer configs should inherit from worker configs
                 Key: KAFKA-6387
                 URL: https://issues.apache.org/jira/browse/KAFKA-6387
             Project: Kafka
          Issue Type: Improvement
          Components: KafkaConnect
    Affects Versions: 1.0.0
            Reporter: Randall Hauch


Currently, the worker configuration file defines the connection properties for the three separate types of connections being made to the Kafka cluster:

# the worker group membership,
# producers for source connectors,
# the consumers for sink connectors. 

The configs are namespaced because to properly support things like interceptors where the configs for 2 and 3 would conflict (same config name, different value).

However, it would be beneficial when such control is not required for the producers and consumers to inherit the top-level configurations yet be able to override them with the {{producer.}} and {{consumer.}} namespaced configurations. This way the producer- and consumer-specific configurations need only be specified if/when they need to override the top-level configurations. This may be necessary, for example, to have different ACLs than the connector tasks compared to the producers and consumers.

This will require a minimal KIP to explain the new behavior. 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)