Search API and various types in one cache

[Mars Man]

I would like to use the Search API of EhCache 2.8 to invalidate (remove) a group of cache entries from cache. In my cache different types of elements and therefor keys are stored. Products, Items, Badges and more. How do I have to define the search attributes in ehcache.xml? I tried one attribute with expression like "key.getProductId()". But putting the first non product element on the cache results into:

net.sf.ehcache.search.attribute.AttributeExtractorException: No such method named "getProductId" present on instance of class ...

How can I solve this problem? Do I have to define a separate cache for each type of element??

Here is a part of my configuration and code:

<searchable keys="true" values="false">
  <searchAttribute name="productId" expression="key.getProductId()" type="Long"/>
</searchable>

Query query = getCache().createQuery().addCriteria(getCache().getSearchAttribute("productId").eq(id)).includeKeys().end();

[Fabien Sanglier]

Of course one solution is to use different caches for different types of objects. If you do that, then it should all work fine using out of box configuration notation.

But if that's not possible or practical, you can go the custom search extractor route where you could register it in the cache, and pick and chose (in custom extractor code) the data to be indexed (and using things like typeof to do A if objects is of type A, and do B if object is of type B etc...

Fabien

--
You received this message because you are subscribed to the Google Groups "ehcache-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ehcache-user...@googlegroups.com.
To post to this group, send email to ehcach...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ehcache-users/07949060-e156-4cd3-9058-58bfbf3e7215%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Fabien Sanglier
fabiens...@gmail.com

[Mars Man]

Thank you for your reply. I've tried the approach with custom extractor in the meanwhile and it solves the problem. But do I have to understand your 2. solution as a recommendation to use one cache for each type of object? Is this a typical setup for EhCache?

Titus


Am Dienstag, 12. April 2016 21:05:09 UTC+2 schrieb Fabien Sanglier:Of course one solution is to use different caches for different types of objects. If you do that, then it should all work fine using out of box configuration notation.

[James House]

Yes, a cache per data type (object class) is typical.

--

You received this message because you are subscribed to the Google Groups "ehcache-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ehcache-user...@googlegroups.com.
To post to this group, send email to ehcach...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ehcache-users/064df44c-55fe-45a5-b3c9-ebee3837ab6c%40googlegroups.com.

[Louis Jacomet]

To add to that, both JSR-107, the standard for caching in Java, and the upcoming Ehcache 3 do offer an API with generic types on caches.

Regards,

Louis

To view this discussion on the web visit https://groups.google.com/d/msgid/ehcache-users/CAB4-RRhryxs86NpOUFhKcE%2BwdtiBGFNatryursf6_51LEW5WVw%40mail.gmail.com.