@artembilan Maybe I am paranoid - but I wanted that the test cannot be derailed by an unclean state in Redis. Unfortunately, the key currently used in the Redis store us not very unique, the adapter's ID is not used right now (the inner_bean issue pointed out earlier).

Also, in case an exception is thrown, or some other Twitter adapter created that same key in Redis, I opted to reset the key upon startup and also do cleanup at the end of the test.

While doing the reset I also discovered that users currently cannot reset the MetaDataStore by removing the key from redis (null values are ignored). This by itself may qualify for a Jira ticket. I wonder in that regard whether we also should expose means to reset a metadata store, e.g. through JMX. What do you think?