Github user dashengju commented on the pull request:
https://github.com/apache/storm/pull/365#issuecomment-68447314
The users of our trident state, they may have a redis or have a redis
cluster. normally, they will not have both.
When they have a redis, they want to use the Jedis client for more
function, such as mget/mset. they do not care about JedisCluster.
When they have a redis cluster, they can just use the JedisCluster client
for single operation.
As redis bolt, because it handle one tuple one time, we provide
JedisCommands is Ok.
As trident state, how about we support more implementations?
1) TridentState/TridentMapState, which provide JedisCommands interface
both for single redis or redis cluster.
2) JedisTridentState/JedisTridentMapState, which provide Jedis interface
just for single redis.
3) JedisClusterTridentState/JedisClusterTridentMapState, which provide
JedisCluster interface, just for redis cluster.
4) ShardedJedisTridentState/ShardedJedisTridentMapState, which provide
ShardedJedis interface.
Users can select what they need. And storm-redis can go along with jedis.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
