Repository: kafka Updated Branches: refs/heads/trunk 3139cc31f -> ed11e177d
TopicConfigManager javadoc references incorrect paths; reviewed by Neha Narkhede Project: http://git-wip-us.apache.org/repos/asf/kafka/repo Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/ed11e177 Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/ed11e177 Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/ed11e177 Branch: refs/heads/trunk Commit: ed11e177d4144a3a803b60f9040ee1bfc17b3b50 Parents: 3139cc3 Author: Aditya Auradkar <[email protected]> Authored: Mon Apr 20 09:27:56 2015 -0700 Committer: Neha Narkhede <[email protected]> Committed: Mon Apr 20 09:28:05 2015 -0700 ---------------------------------------------------------------------- core/src/main/scala/kafka/server/TopicConfigManager.scala | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kafka/blob/ed11e177/core/src/main/scala/kafka/server/TopicConfigManager.scala ---------------------------------------------------------------------- diff --git a/core/src/main/scala/kafka/server/TopicConfigManager.scala b/core/src/main/scala/kafka/server/TopicConfigManager.scala index 47295d4..b675a7e 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/<topic_name>/config + * /config/topics/<topic_name> * 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/<topic_name>/config path. + * /config/changes/config_change_13321 + * This is just a notification--the actual config change is stored only once under the /config/topics/<topic_name> 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
