Of course you should. But have in mind what currently Ignite will download full result set to client node to produce final result set if query is executed in distributed mode (having setLocal(false)), and you have very large result set.
You should consider adding something like limit clause to the query. 2016-06-03 9:28 GMT+03:00 jan.swaelens <[email protected]>: > Sure I can give that a try, so I start multiple nodes and define a > collocation key on the tables being joined together (from the many object > to > the single cardinality ones)? > > The data is being pulled to populate a work list for users, sort of a jira > issue list for example. So the data goes to the client app eventually. > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Unexpected-performance-issue-with-SQL-query-followed-by-error-tp4726p5398.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best regards, Alexei Scherbakov
