[ 
https://issues.apache.org/jira/browse/STORM-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Satish Duggana updated STORM-2220:
----------------------------------
    Description: Currently Cassandra bolts takes cassandra cluster 
configuration fro storm topology configuration. This is restrictive once it has 
two different cassandra bolts talking to different cassandra endpoints. Give a 
way to pass cassandra conf to any cassandra bolt.   (was: Currently Cassandra 
bolts takes cassandra cluster configuration fro storm topology configuration. 
This is restrictive once it has two different cassandra bolts talking to 
different cassandra endpoints. It is better to follow configKey approach like 
HBase bolts. This will allow users to configure different cassandra endpoints 
in a topology and they can be referred by multiple bolts.)

> Adding config keys for CassandraBolts instead of taking at topology level 
> configuration.
> ----------------------------------------------------------------------------------------
>
>                 Key: STORM-2220
>                 URL: https://issues.apache.org/jira/browse/STORM-2220
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-cassandra
>    Affects Versions: 2.0.0, 1.x
>            Reporter: Satish Duggana
>            Assignee: Satish Duggana
>             Fix For: 2.0.0, 1.x
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently Cassandra bolts takes cassandra cluster configuration fro storm 
> topology configuration. This is restrictive once it has two different 
> cassandra bolts talking to different cassandra endpoints. Give a way to pass 
> cassandra conf to any cassandra bolt. 



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

Reply via email to