[ 
https://issues.apache.org/jira/browse/STORM-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554849#comment-14554849
 ] 

Sumit Chawla edited comment on STORM-817 at 5/21/15 6:56 PM:
-------------------------------------------------------------

Hi Zhuo

My use case matches "a".  We have multiple topics separated by tenant 
namespaces.  We want to be able to run a aggregation stream for data coming 
from all tenants. Tenants get added dynamically.  So new kafka topics get 
created.  All the topics will be matching a regex pattern. 
 example:
     clickstream:tenant1:log
     clickstream:tenant2:log
     clickstream:tenant3:log

Storm code should be able to perform auto-discovery, and should be able to to 
fetch from newly created topics in run time.

What do you think will be the size of this effort?  I am also willing to put in 
sometime in feature.  May be we can collaborate on this.






was (Author: sumitkchawla):
Hi Zhuo

My use case matches "a".  We have multiple topics separated by tenant 
namespaces.  We want to be able to run a aggregation stream for data coming 
from all tenants. Tenants get added\removed dynamically.  So new kafka topics 
get created.  All the topics will be matching a regex pattern. 
 example:
     clickstream:tenant1:log
     clickstream:tenant2:log
     clickstream:tenant3:log

Storm code should be able to perform auto-discovery, and should be able to to 
fetch from newly created topics in run time.

What do you think will be the size of this effort?  I am also willing to put in 
sometime in feature.  May be we can collaborate on this.





> Kafka Wildcard Topic Support
> ----------------------------
>
>                 Key: STORM-817
>                 URL: https://issues.apache.org/jira/browse/STORM-817
>             Project: Apache Storm
>          Issue Type: New Feature
>          Components: storm-kafka
>            Reporter: Sumit Chawla
>
> Creating a feature request for supporting Wildcard Topic's for Kafka Spout.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to