On Sat, Jan 17, 2015 at 6:51 AM, Sergi Vladykin <[email protected]> wrote:
> > In my view, using IngiteBiPredicate<K, V> instead of > > IgnitePredicate<Cache.Entry<K, Vl>> is easier to read and is more > > > > Then it is better to introduce CachePredicate<K,V> for entry if readability > is your main concern. > > > > consistent with EntryProcessor<K,V> design from JCache. > > > > As far as I see EntryProcessor has the following signature: T > process(MutableEntry<K, V> entry, Object... arguments) > it is definitely more consistent with my approach. > > The main reason why I want it to be entry but not just K,V is better > generalization level. For example it will be possible to check entry > version in predicate, etc... > Hm... I didn't notice MutableEntry. I think it makes the putIf methods redundant then, since you can call MutableEntry.setValue(...) method. However, there is a ticket to remove all extra methods from Ignite cache entry: https://issues.apache.org/jira/browse/IGNITE-96 . Let's start another discussion whether it should not have any extra methods. > > Sergi >
