he scenario described could be a valid
> one. And it is for you to evaluate whether this is the expected behavior or
> a bug.
>
> Thank you.
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-near-cache-conf
e in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-near-cache-conflicts-with-server-distributed-cache-tp4768p4792.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Best regards,
Alexei Scherbakov
http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-near-cache-conflicts-with-server-distributed-cache-tp4768p4792.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
to
>
> https://apacheignite.readme.io/docs/clients-vs-servers#creating-distributed-caches
> ,
> calling Ignition.start(igniteConfiguration) first time, will create a
> distributed server cache. And client.createNearCache() will create the near
> cache for that specific node's client.
&g
n context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-client-near-cache-conflicts-with-server-distributed-cache-tp4768.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
