kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Hauch (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-6387) Worker's producer and consumer configs should inherit from worker configs
Date Mon, 08 Jan 2018 19:21:00 GMT

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

Randall Hauch resolved KAFKA-6387.
    Resolution: Won't Fix

Because of the inability to maintain backward compatibility of the behavior, I'm withdrawing
this request and marking this issue as WONTFIX.

> 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
>              Labels: needs-kip
> 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

View raw message