Hi. I was looking into state management <http://storm.apache.org/releases/1.0.2/State-checkpointing.html> which looks like a really cool feature but I am wondering if it'd be right for my use case. One of the bolts does bulk updates to database and stores the update information temporarily in hashmap. Once the update is done, the map is cleared. If the worker crashes, the update data is lost so I want to persist update information across restarts using RedisKeyValueState <https://github.com/apache/storm/blob/99a11cb2890b273520cd29cffb5806f5111abeb6/external/storm-redis/src/main/java/org/apache/storm/redis/state/RedisKeyValueState.java>. I could use get/put to modify individual values in KeyValueState but the interface doesn't expose any method to clear *all *values in the KeyValueState. So I am wondering if state management is not the right tool here and what's the appropriate use of state management. Any insight on this would be great.
Thanks. -- Abhishek
