You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Satish Duggana (JIRA)" <ji...@apache.org> on 2016/11/28 06:32:58 UTC
[jira] [Updated] (STORM-2220) Adding config keys for CassandraBolts
instead of taking at topology level configuration.
[ 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. 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
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)