You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Shikhar Bhushan (JIRA)" <ji...@apache.org> on 2016/07/13 22:52:20 UTC
[jira] [Created] (KAFKA-3962) ConfigDef support for
resource-specific configuration
Shikhar Bhushan created KAFKA-3962:
--------------------------------------
Summary: ConfigDef support for resource-specific configuration
Key: KAFKA-3962
URL: https://issues.apache.org/jira/browse/KAFKA-3962
Project: Kafka
Issue Type: Improvement
Reporter: Shikhar Bhushan
It often comes up with connectors that you want some piece of configuration that should be overridable at the topic-level, table-level, etc.
There are a couple of possible ways to allow for this:
1. Support for map-style config properties "k1:v1,k2:v2". There are escaping considerations to think through here. Also, how should the user override fallback/default values -- perhaps {{*}} as a special resource?
2. Templatized configs -- so we can define {{$resource.some.property}} with the ConfigDef API, and have getter variants that take the resource argument. The default value is more naturally overridable here, by the user setting {{some.property}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)