Sorry i missed this response. The problem was actually that I was not
setting null correctly in binary objects so the schema kept updating in all
the nodes over and over. woops
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Disabling-client-notifications
What notifications are you referring to? Events are disabled by default in
Ignite and can be sent to a client only if they are enabled and if you have
a remote listener for them.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Disabling-client
I meant to say the cache is loaded by
ignite.cache(cacheName).loadCache(null);
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Disabling-client-notifications-tp8704p8705.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ehind, but I'd rather just not let the client get
behind.
Any ideas?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Disabling-client-notifications-tp8704.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
