I skimmed some files of storm-redis, but I'm still curious that what's the key point from storm-redis. So I have some questions.
- Is Redis for skipping completed tuples when root tuple is replayed, or continue processing tuple from last state? - Do users need to handle states it by his/her hand? - Does it still beat Storm if failing tuple rate is very low or none? - Can we still get a higher throughput when we drop Redis? (In case of not collaborating with Redis with some situation, for example, license issue) In addition, Calculator.java seems to a user-defined bolt, but it communicates to Redis directly to store states of tuple, which it should be hidden. It seems to lack something to use it for general purposes. ps. I encourage you to use latest Jedis, which has fixed many bugs since 2.2.1. Latest version is 2.6.0, and hopefully we'll release 2.6.1 in a few days. 2014-11-04 5:31 GMT+09:00 Abhishek Bhattacharjee < [email protected]>: > Hi, > We ( me and the CCed persons) are maintaining a project on github > which manages to implement stateful-ness in storm. > > We have got some encouraging results through our benchmarking. > We would like to know what more could be done so that the project could > be inculcated into @stormprocessor > > Github link for our project: https://github.com/pict2014/storm-redis > > We are hoping for a reply. > > Cheers, > *Abhishek Bhattacharjee* > *Pune Institute of Computer Technology* > -- Name : 임 정택 Blog : http://www.heartsavior.net / http://dev.heartsavior.net Twitter : http://twitter.com/heartsavior LinkedIn : http://www.linkedin.com/in/heartsavior
