Re: [infinispan-dev] Proposed ISPN 7 compilation incompatibilities with ISPN 6

On Thu, Mar 13, 2014 at 8:37 AM, Pedro Ruivo <pedro(a)infinispan.org&gt; wrote: > > > On 03/13/2014 12:35 PM, William Burns wrote: >> On Thu, Mar 13, 2014 at 8:31 AM, Pedro Ruivo <pedro(a)infinispan.org&gt; wrote: >>> Hi, >>> >>> #1 and #2 are ok to me but, IMO, the filter package should be in commons >>> module >> >> Sorry I forgot to detail why I said core. I originally planned for >> commons package as well, however the KeyValueFilter class needs the >> Metadata class, which doesn't live in the commons package. I didn't >> want to separate the 2 filter classes. And unfortunately the Metadata >> class relies on other classes in core, so that isn't easy to move over >> either, but doable :( WDYT? > > can you explain why the metadata is needed? I assumed that the key and > the value were the only objects needed. That is how the design doc was written up :P My guess is so that people if needed can filter out versioned entries or to possibly do some eviction magic since they can try to calculate when the entry would be removed. Maybe Mircea can shed some additional light.