The issue is fixed and is in master already. You can wait for Ignite 2.7 release or check that the issue is resolved with nightly release [1]
[1] - https://ci.ignite.apache.org/project.html?projectId=Releases_NightlyRelease Best Regards, Igor On Tue, Oct 16, 2018 at 10:42 AM wt <waynethe...@gmail.com> wrote: > Thank you Igor > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
