[
https://issues.apache.org/jira/browse/STORM-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313522#comment-15313522
]
ASF GitHub Bot commented on STORM-1875:
---------------------------------------
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1459
The problem is actually not simple. The blocking point is JedisCommands
interface, not config.
JedisCommands exposes operations which use only single key. Since some
multiple keys operations of Redis is not suitable for Redis Cluster (operation
is available but not making sense), Jedis and JedisCluster takes different
interfaces, which blocks us to provide unified interface from storm-redis side.
One simple way is separating existing classes to RedisLookupBolt /
RedisClusterLookupBolt, RedisStoreBolt / RedisClusterStoreBol, as
State/MapState did, but it incurs backward incompatibility if users use
RedisLookupBolt / RedisStoreBolt to access Redis Cluster.
> Separate Jedis/JedisCluster Config
> ----------------------------------
>
> Key: STORM-1875
> URL: https://issues.apache.org/jira/browse/STORM-1875
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-redis
> Affects Versions: 1.0.0, 1.0.1, 1.0.2
> Reporter: darion yaphet
>
> Separate Jedis / JedisCluster to provide full operations for each environment
> to users .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
