This appears to be a problem that is fixed in Ignite 2.7.


--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to