Uh oh!
There was an error while loading. Please reload this page.
[STORM-1875]Separate Jedis/JedisCluster Config - #1459
Conversation
The problem is actually not simple. The blocking point is JedisCommands interface, not config. One simple way is separating existing classes to RedisLookupBolt / RedisClusterLookupBolt, RedisStoreBolt / RedisClusterStoreBolt, as State/MapState did, but it incurs backward incompatibility if users use RedisLookupBolt / RedisStoreBolt to access Redis Cluster. |
HeartSaVioR
commented
Jun 3, 2016
One other way without breaking compatibility but not beauty is adding some utility methods to AbstractRedisBolt like, and let users convert their JedisCommands instance to actual type before using full features. |
Both Just use (We have support some command like |
@darionyaphet DISCLAIMER: I'm also a committer of Jedis. :) |
darionyaphet
commented
Jun 5, 2016
|
HeartSaVioR
commented
Jun 5, 2016
No for predefined operations (StoreBolt, LookupBolt) but we can still support full features for AbstractRedisBolt and let users extend this class. |
darionyaphet
commented
Jun 5, 2016
OK , I will try to separating classes :D |
STORM-1875
Separate Jedis / JedisCluster to provide full operations for each environment to users .