Hi Jan, I would suggest double-checking that the most selective indexes are chosen by Ignite SQL engine and there are no full scans during a SQL query execution.
To fulfill this you can use "EXPLAIN" statement to see an execution plan of every query [1]. If a index is not optimally selected for a query then you can create a group index if needed [2]. [1] https://apacheignite.readme.io/docs/sql-queries#using-explain [2] https://apacheignite.readme.io/docs/sql-queries#section-group-indexes -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unexpected-performance-issue-with-SQL-query-followed-by-error-tp4726p4760.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
