Performance problems while running SQL query involving JOINS and ORDER BY eventually leading to heap OOME.

[gourav10041996]

We are facing a severe performance issue with Ignite SQL select JOIN queries
when using Order By clause.
This occurs when the column used for Order By is not one of the columns in
the where clause.  

SELECT *
FROM  CACHE1 C1, CACHE2 C2  
WHERE C1.JOINCol = C2.JOINCol AND C1.COL1 = 'someValue'
ORDER BY C1.COL2

In this situation, it looks like the index available on the order by column
(C1.COL2) is not used by SQL engine.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/