[
https://issues.apache.org/jira/browse/KAFKA-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496810#comment-14496810
]
Parth Brahmbhatt commented on KAFKA-2035:
-----------------------------------------
It does and if I understand correctly you are proposing to create something
like the following
class Topic(val config:TopicConfig, val logs:Set[Log] ., <all other topic
related stuff>).
I am not sure why this does not exist right now but I think moving in that
direction is a good idea. At the same time I also think this will be a lot more
work and we can probably take incremental approach without a lot of(or probably
any) throw away work by starting to model one piece at a time so other jiras
don't need to be blocked until we settle on a top level Topic model. After all
the top level Topic will just be a composition of all these small things that
make up a topic.
If you think it is essential to nail the Topic structure before making progress
on this jira and other related jira let me know and I can file a new jira for
the same.
> 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)
