I also want to point out that Ignite has nightly builds, so you can try them instead of doing your own build as well.
https://ignite.apache.org/download.cgi#nightly-builds D. On Thu, Aug 16, 2018 at 1:38 AM, Vladimir Ozerov <voze...@gridgain.com> wrote: > Hi, > > There were a lot of changes in the product since 2.3 which may affect it. > Most important change was baseline topology, as already mentioned. > I am aware of a case when incorrect result might be returned [1], which is > already fixed in *master*. Not sure if this is the same issue, but you > may try to build Ignite from recent master and check if the problem is > still there. > > Is it possible to create isolated reproducer for this issue? > > [1] https://issues.apache.org/jira/browse/IGNITE-8900 > > On Wed, Aug 15, 2018 at 11:34 PM bintisepaha <binti.sep...@tudor.com> > wrote: > >> Thanks for getting back, but we do not use Ignite's native persistence. >> Anything else changed from 2.3 to 2.4 to cause this around SQL Queries? >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >
