Hi Team, I just would like to check if there is a plan to relook into these behavior ?
Thanks. On 13 February 2017 at 09:29, Anil <[email protected]> wrote: > Hi Val, > > When two cache's require a join, collocation must be true in jdbc > connection and then group by queries on individual caches will not return > aggregated results. you mean this is not limitation ? if Yes, i am sorry, > i may not agree on this :( > > in this case, to make sql queries work, two jdbc client must be created.. > one for queries of individual cache and other for join queries. > > Thanks > > > > On 13 February 2017 at 07:56, vkulichenko <[email protected]> > wrote: > >> Anil, >> >> I don't see any limitations (except IGNITE-3860). Aggregation without >> collocation works properly and return correct result unless collected flag >> is set to true (doing so in this scenario is a misuse). As for >> performance, >> collocated execution will always be faster than non-collocated. That's >> true >> for any distributed system and there is no magic, you know :) >> >> -Val >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/NOT-IN-in-ignite-tp9861p10582.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
