[
https://issues.apache.org/jira/browse/KAFKA-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628392#comment-14628392
]
Ashish K Singh edited comment on KAFKA-2275 at 7/15/15 5:25 PM:
----------------------------------------------------------------
[~onurkaraman] I think your suggestion makes sense, but I too have the same
question as [~hachikuji], is there any particular use case that will benefit
from having the API return a future?
was (Author: singhashish):
[~onurkaraman] I think your suggestion makes sense, but I too have the same
question as [~hachikuji], is there any partivular use case that will benefit
from having the API return a future?
> Add a ListTopics() API to the new consumer
> ------------------------------------------
>
> Key: KAFKA-2275
> URL: https://issues.apache.org/jira/browse/KAFKA-2275
> Project: Kafka
> Issue Type: Sub-task
> Components: consumer
> Reporter: Guozhang Wang
> Assignee: Ashish K Singh
> Priority: Critical
> Fix For: 0.8.3
>
>
> With regex subscription like
> {code}
> consumer.subscribe("topic*")
> {code}
> The partition assignment is automatically done at the Kafka side, while there
> are some use cases where consumers want regex subscriptions but not
> Kafka-side partition assignment, rather with their own specific partition
> assignment. With ListTopics() they can periodically check for topic list
> changes and specifically subscribe to the partitions of the new topics.
> For implementation, it involves sending a TopicMetadataRequest to a random
> broker and parse the response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
