Hi Val, Do you guys accept this behavior as bug ? correct it so that group by with non affinity key returns same results with/without collocated true ?
Thanks. On 9 February 2017 at 09:40, Anil <[email protected]> wrote: > Hi Val, > > You are right. i collocated the data and set the collocated = true. and it > impacted my group by queries. > > I was mentioning only group by queries on non affinity key field as an > issue. > > Thanks. > > On 9 February 2017 at 03:18, vkulichenko <[email protected]> > wrote: > >> Anil, >> >> You should always try to colocate as much as possible when working with a >> distributed system. If you colocate properly and set collocated=true, you >> will get correct result with the best possible performance. If you can't >> colocate, you have to set the flag to false. Result will still correct, >> but >> it will work slower. In other words, this is just an optional performance >> optimization. >> >> Not colocating and setting flag to true is a misuse as this combination >> leads to incorrect result. >> >> -Val >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/NOT-IN-in-ignite-tp9861p10506.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
