Hi Val,
Thanks for your reply.
#1 My Request maybe somewhat different with IGNITE-3699.
see below case:
Suppose Ignite already have several cache entries. simply, we set each cache entry will expire in one day.
at one moment , the caches in ignite will have different expiry time, for they are put into ignite in different time. Let's say, entry1 with key "key1" will expire in 12 hours,entry2 with key "key2" will expire in 2 hours. now
we restart ignite servers. after ignite server startup, we restore all caches. for cache entry1 we want to set it expire in 12 hours while not one day. and for entry2 we want to set it expire in 2 hours.
current 1.8 interface, it doesn't support this operation.
public abstract class CacheStoreAdapter<K, V> implements CacheStore<K, V> {
...
public void loadCache(IgniteBiInClosure<String, BinaryObject> clo, Object... args)
{
...
}
}
I don't know IGNITE-3699 will fix it or not.
#2 what's the workaround solution for this, if we can't wait release of 2.0?
if we call cache.put/putAll in cacheLoad, it is allowed? if allowed, what's the side effect?
or simply just call cache.put/putAll in client side.
Thanks
Shawn
On 02/11/2017 06:32，vkulichenko<[email protected]> wrote：
Hi,
When done right, expiry policy provided in CacheConfiguration must be
applied to entries loaded from store. However there was an issue that was
fixed recently (not released yet):
https://issues.apache.org/jira/browse/IGNITE-3699
As for NPE, not sure why this happens. What is null there?
-Val
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/loadCache-with-ExpiryPolicy-tp10544p10557.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
