[ https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252850#comment-14252850 ]
ASF GitHub Bot commented on STORM-391: -------------------------------------- Github user harshach commented on the pull request: https://github.com/apache/storm/pull/338#issuecomment-67593515 @Lewuathe Sorry looks like I am not clear . From above discussion it seems you want to check kafka zookeeper /topics path to check if a topic exists or not. As per previous discussion I would like to see if you can use kafka api exceptions instead of relying zookeeper path for checking if topic exists. Is this the approach you are taking ? > 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)