[
https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236587#comment-14236587
]
ASF GitHub Bot commented on STORM-391:
--------------------------------------
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/338#issuecomment-65885304
I agree with Sriharsha. The current code relies too heavily on kafka's
internal zk metadata storage. This is fragile, we should not be depending
directly on any of the kafka's internal metadata details. Given we have APIs
available to get the same information, it is better to rely on them.
> KafkaSpout to await for the topic
> ---------------------------------
>
> Key: STORM-391
> URL: https://issues.apache.org/jira/browse/STORM-391
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 0.9.2-incubating
> Reporter: Alexey Raga
> Assignee: Kai Sasaki
> Labels: features
>
> When topic does not yet exist and the consumer is asked to consume from it,
> the default behaviour for Kafka heigh-level consumer is to "await" for the
> topic without a failure.
> KafkaSpout currently fails trying to get the partition information about the
> topic that does not exist.
> It may be a good idea to have the same common behaviour in KafkaSpout and it
> can probably be implemented through the zookeeper watchers: if topic does not
> exist, then set up a watcher and don't do anything until it yields.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
