Looking for a cache key without postponing the expiriation by maxIdle on RHDG 7
Issue
I wonder if it is possible somehow to look for a key
in a distributed cached
without the property max-idle
postpone the expiration of that entry once is hit via Hot Rod
client. Does it exist any option in JDG
to change the default behavior of methods get
or contains
?
Environment
- Red Hat Data Grid
- 7.1.2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.