Igniters,
FYI: next Wednesday, December 9 2020 at 21:00 UTC+3 I am giving an Apache
Ignite Workshop "Developing Applications That Are Easy to Manage". Use this
link to register:
https://www.gridgain.com/resources/webinars/apache-ignite-workshop-developing-applications-are-easy-manage
Abstract
Hi,
use:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/IgniteConfiguration.html#setConsistentId-java.io.Serializable-
to set the consistent id.
Thanks, Alex
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Finally found the issue.
In the thin client configuration I had only one port provided to connect
to the server nodes. As soon as I provided the default range
(10800-10900) the connections seemed to behave better. This resolved the
issue somehow.
However I tried it out at the cluster on the
Thank you for the clarification!
For this use case where data is being pulled from an underlying RDBMS and
instantiated as an Associate object, is it possible to work the Associate
object as a Binary Object similar to what you've done here?
Also, I see than in Vladamir's loading example, he uses
> are there C# equivalencies to the Java interfaces BinaryObject and
Affinity
Yes, please see IIgnite.GetAffinity [1] and GetBinary [2].
[1]
https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.IIgnite.html#Apache_Ignite_Core_IIgnite_GetAffinity_System_String_
[2]