[
https://issues.apache.org/jira/browse/KAFKA-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-2035:
-----------------------------
Status: In Progress (was: Patch Available)
[~parth.brahmbhatt] Unless you object I'd prefer to either figure out the
desired end state with respect to topic's and build towards that or else leave
it as is and just add this to the log config. Either way we can file that Topic
refactoring JIRA even if it just as a placeholder for thoughts on the subject.
> Add a topic config cache.
> -------------------------
>
> Key: KAFKA-2035
> URL: https://issues.apache.org/jira/browse/KAFKA-2035
> Project: Kafka
> Issue Type: Task
> Reporter: Parth Brahmbhatt
> Assignee: Parth Brahmbhatt
> Attachments: KAFKA-2035_2015-03-31_10:52:12.patch
>
>
> Currently the topic config is all about Log configuration so we have a
> TopicConfigManager which takes in a Log instance and keeps updating that
> instance's config instance as and when the topic config is updated. The topic
> config update notifications are sent using zk watchers by Controller.
> I propose to introduce a TopicConfigCache which will be updated by
> TopicConfigManager on any config changes. The log instance and any other
> component (like the authorizer mentioned in KAFKA-1688) will have a reference
> to TopicConfigCache using which they will access the topic configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
