Re: PeerClassLoading example using cacheLoaders

ate.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> > > > -- > View this message in context: Re: PeerClassLoading example using > cacheLoaders > <http://apache-ignite-users.70518.x6.nabble.com/PeerClassLoading-example-using-cacheLoaders-tp16136p16177.html> > Sent from the Apache Ignite Users mailing list archive > <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com. >

Re: PeerClassLoading example using cacheLoaders

Hi, You are right, *load* method is called when there is a miss in a cache. putIfAbsent is supported by IgniteCache out of the box. I'm afraid that there is no simple way to achieve what a CacheStore offers. With any other approach, you would have to sacrifice read/write-through behavior. Kind r

Re: PeerClassLoading example using cacheLoaders

Thank you,very much. And one more question, The load method of cacheLoader is called when I do get from cache with the key which does not exists. Isn't it? Isnt it solution without passing chacheLoader -I do get and if the key is absent ,do put that key in the cache,in other words do putI

Re: PeerClassLoading example using cacheLoaders

If you have a custom implementation of CacheLoader, you need to deploy this implementation on all nodes. I'm afraid, there is no workaround. Note that Ignite provides CacheStore implementations for RDBMS [1] and Cassandra [2] out of the box, so there is a chance that you don't need custom one in t

Re: PeerClassLoading example using cacheLoaders

Hi I know it. I dont want to copy that classes to all nodes.Therefore I dont want to use chackeLoaderFactories. I am searching other solution. Now I want to remove loaders. How to organize my cache creation without loaders,but keep the logic in loaders,where to put that logic Thank you -

Re: PeerClassLoading example using cacheLoaders

Hi, Peer class loading works only for compute closures and tasks as described here . it's not applicable for configuration classes or cache entries, so you have to copy that classes to all nodes. Kind regards, Alex. On Fri, Aug 11, 2017 at 3: