Re: [infinispan-dev] TreeCache needs Flag(s) to be maintained for the duration of a batch/tx

On 4 Jan 2011, at 17:20, Sanne Grinovero wrote: > We had a similar issue in the past: > Even when using Flag.SKIP_STORE consistently on a specific type of > object, which I did want to absolutely prevent to be written to the > store, this could end up in the store during rehash operations as the > flag wouldn't be in the context at that moment, and for safety the new > owner will write to the store. > This forced me to change the Lucene Directory to use multiple caches, > to be able to configure the specific one without any store. > > Maybe we could attach some flags to Entry, possibly of different type > than current Flag. For example it would be nice to have a > "NEEDS_STORE" which could be set to false as soon as it's written, and > so also have rehashing perform better as there's no need to rewrite to > the store for most of the data being received, as it's likely already > stored. Rehashing should bypass writing to a CacheStore anyway, if the store is shared.  If this is not the case, then that is a bug.