[
https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240721#comment-14240721
]
ASF GitHub Bot commented on STORM-391:
--------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/338#issuecomment-66410673
Sorry I don't know Kafka, but I feel that it's going weird.
Relying on other component's internal is real things to avoid.
Components try its best to keep compatibility with APIs, but not internal.
Think about Kafka internal has changed. It means Storm-Kafka could only
support some version range. newer, or older. And it would be easily broken
again.
How about requesting/contributing some new API that can check existence of
topic to Kafka project? If it's already exist but slow, we can find out why it
should be slow, from Kafka project.
> 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)
