You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Scott Kruger (JIRA)" <ji...@apache.org> on 2016/07/13 14:15:20 UTC
[jira] [Commented] (KAFKA-2205) Generalize TopicConfigManager to
handle multiple entity configs
[ https://issues.apache.org/jira/browse/KAFKA-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375073#comment-15375073 ]
Scott Kruger commented on KAFKA-2205:
-------------------------------------
Looks like this isn't *quite* fixed all the way. {{DynamicConfigManager.processNotification}} still reports that {{entity_type}} should be {{topic}} or {{client}}, not the correct pluralized forms. I ran into this when manually updating configs directly in zookeeper.
> Generalize TopicConfigManager to handle multiple entity configs
> ---------------------------------------------------------------
>
> Key: KAFKA-2205
> URL: https://issues.apache.org/jira/browse/KAFKA-2205
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Aditya Auradkar
> Assignee: Aditya Auradkar
> Labels: quotas
> Fix For: 0.9.0.0
>
> Attachments: KAFKA-2205.patch, KAFKA-2205_2015-07-01_18:38:18.patch, KAFKA-2205_2015-07-07_19:12:15.patch, KAFKA-2205_2015-07-14_10:33:47.patch, KAFKA-2205_2015-07-14_10:36:36.patch, KAFKA-2205_2015-07-17_11:14:26.patch, KAFKA-2205_2015-07-17_11:18:31.patch, KAFKA-2205_2015-07-24_18:11:34.patch
>
>
> Acceptance Criteria:
> - TopicConfigManager should be generalized to handle Topic and Client configs (and any type of config in the future). As described in KIP-21
> - Add a ConfigCommand tool to change topic and client configuration
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)