You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by endianignite <en...@gmail.com> on 2016/04/01 09:34:58 UTC
CacheStoreBalancingWrapper is not serializable
Should I make CacheStoreBalancingWrapper serializable, or is there a reason
not to?
If no objections I will raise a JIRA and make the change.
--
View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/CacheStoreBalancingWrapper-is-not-serializable-tp8215.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Re: CacheStoreBalancingWrapper is not serializable
Posted by Alexey Goncharuk <al...@gmail.com>.
Any reason you want to make it serializable? This is an internal class and
it is never transmitted over the network to a remote node. As Yakov pointed
out, cache store factory is what being transmitted to remote nodes with the
configuration.
Re: CacheStoreBalancingWrapper is not serializable
Posted by Yakov Zhdanov <yz...@apache.org>.
Store may be non-serializable, but factory should be. Singleton factories
serialized along with their instances in my understanding suitable only for
tests or pre-configured caches.
--Yakov
2016-04-01 10:34 GMT+03:00 endianignite <en...@gmail.com>:
> Should I make CacheStoreBalancingWrapper serializable, or is there a reason
> not to?
>
> If no objections I will raise a JIRA and make the change.
>
>
>
> --
> View this message in context:
> http://apache-ignite-developers.2346864.n4.nabble.com/CacheStoreBalancingWrapper-is-not-serializable-tp8215.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>