Currently I'd recommend not to use group indexes for conditions other than equality.
Sergi 2015-08-20 0:59 GMT+03:00 Sergi Vladykin <[email protected]>: > Thanks for the test case! > It is a bug related to null value sorting, it will be fixed in the next > release. > > Sergi > > 2015-08-18 16:12 GMT+03:00 alex.glau <[email protected]>: > >> Hi Sergi, >> >> I've prepared simple example that reproduces the discussed query problem. >> 1. take example in: >> >> https://github.com/alex-glau/bt9_examples/tree/master/Examples/src/com/bt9/test >> >> 2. it includes: >> - main class ShipmentSearchTest >> - two classes representing cache type: CachedShipment and >> CachedShipmentSegment >> - two enum classes >> >> 3. When you run main class >> - two Ignite caches are loaded and loaded instances are printed to >> console >> - three query methods are executed: >> >> query_1() - includes criteria "startDate > ?" and returns wrong result >> (0 instead of 3) >> query_2() - includes criteria "startDate < ?" and returns right >> result 3 >> query_2() - includes both criteria "startDate > ?" and "startDate < ?" >> and returns right result 3 >> >> What is wrong in query_1? >> >> Regards, >> Alex >> >> >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/Performance-of-join-SQL-queries-tp845p1033.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
