From ed11e177d4144a3a803b60f9040ee1bfc17b3b50 Mon Sep 17 00:00:00 2001 From: Aditya Auradkar Date: Mon, 20 Apr 2015 09:27:56 -0700 Subject: [PATCH] TopicConfigManager javadoc references incorrect paths; reviewed by Neha Narkhede --- core/src/main/scala/kafka/server/TopicConfigManager.scala | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/core/src/main/scala/kafka/server/TopicConfigManager.scala b/core/src/main/scala/kafka/server/TopicConfigManager.scala index 47295d40131..b675a7e45ea 100644 --- a/core/src/main/scala/kafka/server/TopicConfigManager.scala +++ b/core/src/main/scala/kafka/server/TopicConfigManager.scala @@ -30,17 +30,17 @@ import org.I0Itec.zkclient.{IZkChildListener, ZkClient} * It works as follows. * * Config is stored under the path - * /brokers/topics//config + * /config/topics/ * This znode stores the topic-overrides for this topic (but no defaults) in properties format. * * To avoid watching all topics for changes instead we have a notification path - * /brokers/config_changes + * /config/changes * The TopicConfigManager has a child watch on this path. * * To update a topic config we first update the topic config properties. Then we create a new sequential * znode under the change path which contains the name of the topic that was updated, say - * /brokers/config_changes/config_change_13321 - * This is just a notification--the actual config change is stored only once under the /brokers/topics//config path. + * /config/changes/config_change_13321 + * This is just a notification--the actual config change is stored only once under the /config/topics/ path. * * This will fire a watcher on all brokers. This watcher works as follows. It reads all the config change notifications. * It keeps track of the highest config change suffix number it has applied previously. For any previously applied change it finds