[
https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243434#comment-14243434
]
ASF GitHub Bot commented on STORM-391:
--------------------------------------
Github user Lewuathe commented on the pull request:
https://github.com/apache/storm/pull/338#issuecomment-66713313
I posted this question on kafka mailing list and found the project for
improvement of kafka api now. I think it is good way to propose check-existence
api to this project.
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Command+Line+and+Related+Improvements
But anyway current storm-kafka depends on kafka metadata on zookeeper
through curator. So I think it is better to solve this issue by using curator
api and then raise ticket about changing the way of exchanging between kafka
and storm-kafka as originally proposed by @lazyval. What do you think all?
> 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)
