This is possible because when you add endpoints to client's configuration
it will use all of them when sending requests (it will send them to random
nodes though). So when you send a large batches of values there won't be
a single node bottleneck, when a single node deals with a great number
of
Hi all,
After taking a look to the c++ thin client source code
(cache_client_impl.cpp) it seems partition awareness is only taken into
account for single requests (Get/Put), but neither for batch (GetAll/PutAll)
nor transactions.
But in our tests, adding endpoints to Ignite Client configuration
