ok, I ask becouse I wont to be sure. Fix will be included in Ignite 2.4 or 2.5?
On the ticket: https://issues.apache.org/jira/browse/IGNITE-7362 in details is write that fix this bug is planning for 2.5 version... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
