If you put a value into a cache, and previous value has already expired, then it will be written to persistent storage once more. It works just like for non-expired entries. Expiry only specifies, when entries are removed from memory, not from persistent storage.
Denis ср, 3 янв. 2018 г. в 14:55, Denis Mekhanikov <[email protected]>: > Hi Mikael! > > Yes, this is fine. Expiration policy is intended to remove those entries > from memory, that are saved to the persistent data storage. > So, if you query expired data one more, it will be loaded from persistence. > > > will any items in the cache that expire and have been modified be saved > before they are removed from the cache ? > Could you clarify this? I didn't really understand the question. > > Denis > > ср, 3 янв. 2018 г. в 14:23, Mikael <[email protected]>: > >> Is it ok to use both third party persistence (setWriteBehindEnabled( >> true)) on a cache and also have an expiration policy set at the same >> time, will any items in the cache that expire and have been modified be >> saved before they are removed from the cache ? >> >> >> >>
