[
https://issues.apache.org/jira/browse/KAFKA-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503297#comment-14503297
]
Parth Brahmbhatt commented on KAFKA-2035:
-----------------------------------------
[~jkreps] yes that is the difference I was referring to. Anyways I think we
don't need to discuss that any more as ACLs are now being pulled out of topic
config (See KIP-11 discussion thread).
I think the the topic owner is useful even outside of security context. I think
it deserves its own config value and I can either add it as a log config (So no
change required, anyone who needs access to owner will now either need a
reference to log instance to get benefit of caching or will have to read from
zookeeper) or we can continue on the path of adding a TopicConfigCache and make
owner a top level entity of that class. Let me know what your preference is.
I did not see a jira to add owner to topics and I can create one if you think
we should discuss that separately.
> 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)
