The issue cannot be reproduced in 1.4.0. It seems the bug was introduced in
1.5.0




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

Reply via email to