[
https://issues.apache.org/jira/browse/KAFKA-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson updated KAFKA-1617:
-----------------------------------
Fix Version/s: (was: 0.10.1.0)
0.10.2.0
> Move Metadata Cache to TopicManager and handling of Offset Request to
> LogManager
> --------------------------------------------------------------------------------
>
> Key: KAFKA-1617
> URL: https://issues.apache.org/jira/browse/KAFKA-1617
> Project: Kafka
> Issue Type: Bug
> Reporter: Guozhang Wang
> Fix For: 0.10.2.0
>
>
> This is a follow-up of KAFKA-1583. In order to make Kafka APIs a pure
> stateless layer that just forwards different requests to the corresponding
> managers, there are still two tasks left:
> 1. Move the metadata cache at KafkaApis to a separate manager, maybe called
> TopicManager, which will be responsible for a) handle topic metadata request,
> b) handle topic metadata update request by talking to replica manager if
> necessary.
> 2. Move the handling logic of offset request to the LogManager, which should
> contain all the information necessary to handle this request.
> Finally, the KafkaApis class should be stateless, meaning no inner variables
> and no start()/shutdown() functions needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
