You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In some cases, a cache entity might be necessarily evicted on cache put.
Describe the solution you'd like
An cachePut operation does evict a current cache entity prior to putting the entity if exists.
The cacheEvict on cachePut is optionally executed only when configured.
The default behavior is not to not evict an entity on cachePut.
Multiple cache region entities are evicted altogether.
an entity on region A mapped by id#1
an entity on region B also mapped by id#1
When the entity of A is put, the entity of B also is evicted because region A and region B are grouped and the cache key(id#1) is identical.
Additional context
An direct db update does not update cache entities, which leads data inconsistency between db and cache storage
The text was updated successfully, but these errors were encountered:
rica-v3
changed the title
CacheEvict on CachePut is optional property
CacheEvict on CachePut is optional property and multiple cache region entities are evicted together.
Feb 28, 2021
Is your feature request related to a problem? Please describe.
In some cases, a cache entity might be necessarily evicted on cache put.
Describe the solution you'd like
An cachePut operation does evict a current cache entity prior to putting the entity if exists.
The cacheEvict on cachePut is optionally executed only when configured.
The default behavior is not to not evict an entity on cachePut.
Multiple cache region entities are evicted altogether.
an entity on region A mapped by id#1
an entity on region B also mapped by id#1
When the entity of A is put, the entity of B also is evicted because region A and region B are grouped and the cache key(id#1) is identical.
Additional context
An direct db update does not update cache entities, which leads data inconsistency between db and cache storage
The text was updated successfully, but these errors were encountered: