First of all I apologise for the late response. I'll try to answer the questions one by one.
> Is Redis for skipping completed tuples when root tuple is replayed, or > > continue processing tuple from last state? It doesn't skip the fully processed tuples it also stores them so that we have a backup of our processing history. > > - Do users need to handle states it by his/her hand? > Yes and No. Using our approach user can delegate the task to the RedisMap class > > - Does it still beat Storm if failing tuple rate is very low or none? > We haven't done the benchmarking for such scenarios. Although, I think it should(or will) not beat storm in such scenarios. > > - 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) I haven't checked that, but if we don't use Redis we can't really save the states. > > 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. > Valid point, we can work towards that to make it more abstract. > It seems to lack something to use it for general purposes. > May be it does, but I think it provides an approach towards statefullness and we can towards the generalisation. > 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. > Okay, will do that :) thanks for the input. From the above lines, I presume that you are working on Jedis, are you also working on Redis directly ? Thanks, -- *Abhishek Bhattacharjee* *Pune Institute of Computer Technology*
