Hi Siva,Thank you for reading my blog post. I have no idea what is the problem in your case, just wanna share some experience.I do not use any user POJOs on the remote nodes. Instead, I create POJO on the thick client node, convert it in BinaryObject and change that object on the remote node by obj
Hi,
I have made a small modification to the ignite-kubernetes module to allow
specification of a port for the IP finder.
To build Ignite, I am using this comment from DEVNOTES.TXT:
mvn clean install -am -Pall-java,all-scala,licenses -DskipTests
This ultimately fails with the following error:
[
The documentation here lists the benefits of enabling Partition Awareness in
thin clients:
https://ignite.apache.org/docs/latest/thin-clients/java-thin-client#partition-awareness
It doesn't say if there are any drawbacks.
1. Are there any drawbacks?
2. If not, why is this not enabled by default
