Class ReadThroughAtlassianCache<K,V>
- All Implemented Interfaces:
ReadThroughCache<K,V>
ReadThroughCache backed by an atlassian-cache Cache.- Since:
- 7.5
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionstatic <K,V> ReadThroughAtlassianCache<K, V> This is essentially an extension method forCache.Retrieves multiple values for the given keys.voidRemovs the cache entry for the given key.voidRemoves all cache entries.Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface com.atlassian.confluence.impl.cache.ReadThroughCache
get
-
Constructor Details
-
ReadThroughAtlassianCache
-
-
Method Details
-
create
public static <K,V> ReadThroughAtlassianCache<K,V> create(com.atlassian.cache.CacheFactory atlassianCacheFactory, CoreCache cacheName) -
getBulk
Description copied from interface:ReadThroughCacheRetrieves multiple values for the given keys. Any entries not already present in the cache will be supplied via the delegate loader.- Specified by:
getBulkin interfaceReadThroughCache<K,V>
-
removeAll
public void removeAll()Description copied from interface:ReadThroughCacheRemoves all cache entries.- Specified by:
removeAllin interfaceReadThroughCache<K,V>
-
remove
Description copied from interface:ReadThroughCacheRemovs the cache entry for the given key.- Specified by:
removein interfaceReadThroughCache<K,V>
-
get
This is essentially an extension method forCache.It provides an overloaded varant of
ReadThroughCache.get(Object, com.atlassian.cache.Supplier)which also takes a predicate which will be used to filter values both (a) after they're loaded from the valueSupplier, and (b) after they're retrieved from the cache.This gives us the concept of the "uncacheable value" as well as the "stale value". These are both caching anti-patterns, but the older code in Confluence is really quite attached to these ideas and doesn't want to give them up, doesn't want to let them down, doesn't want to turn around and forget them.
Note also that the atlassian-cache API has no such concepts, i.e. the value supplier cannot return null, and whatever the supplier returns will always be added to the cache. In order to work around this, we use exceptions to escape from the stack (I know, I know, don't @ me), which are then caught and decoded. It's butt ugly, but it's contained within this doozy of a method and won't leak out.
- Specified by:
getin interfaceReadThroughCache<K,V> - Parameters:
key- the key to resolve in the cachevalueSupplier- ASupplierwhich will be called if there is no value in the cache (may return null).valueTester- APredicatethat will be used to test the validity of any value in the cache or loaded from the supplier- Returns:
- the cached value, or the value which was loaded from the supplier (may be null)
-