[infinispan-dev] manual eviction and indexing

[Adrian Nistor]

I Agree. If  indexing + (automatic) eviction + no cachestore is 
currently allowed, then we should add a jira to add this config validation.

But what about manual eviction? Would it make sense to handle it the way 
I did?

On 12/11/2013 02:32 PM, Sanne Grinovero wrote:
> Hi Adrian,
> +1 good catch.
>
> but what's a realistic use case for {indexing + eviction + no cachestore} ?
> I guess some use cases might exist but I don't think it's critical,
> would you agree?
>
> and what about automatic eviction?
>
> I think the guiding principle should be that if an entry can be
> retrieved by key it should be searchable, and vice-versa, if I can
> find it by running a query I should be able to load the result.
> So expiry and other forms of eviction should also be considered, but
> if there is no practical use case we can consider making this an
> illegal configuration or simply log a warning about the particular
> configuration.
>
> Sanne
>
> ----- Original Message -----
>> Hi Sanne,
>>
>> I found that manual eviction does not update the index. I think manual
>> eviction should behave like a remove, if there are no cache stores
>> configured.
>>
>> Here's a test and a 'fix' :)
>> https://github.com/anistor/infinispan/tree/t_manual_evict_and_indexing
>>
>> Let's discuss this when you have time.
>>
>> There is also the more complex situation of in-DataContainer eviction ...
>>