Hello! This is unfortunate. Do we have a ticket for it?
As a workaround, one may set query warning timeout to 1 ms and then see these detailed messages in the log. Regards, -- Ilya Kasnacheev чт, 17 июн. 2021 г. в 14:31, <[email protected]>: > Actually this is true that neither plain explain nor explain analyze shows > the number of scanned rows. This information is only available when ignite > shows the warning about query exceeding time limits. > > Regards, > Ivan > > From: Ilya Kasnacheev <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Thursday, June 17, 2021 at 1:04 PM > To: "[email protected]" <[email protected]> > Subject: Re: SQL EXPLAIN ANALYZE > > Hello! > > What happens if you just do EXPLAIN <QUERY>? > > Regards, > -- > Ilya Kasnacheev > > > пт, 11 июн. 2021 г. в 14:34, Devakumar J <[email protected] > <mailto:[email protected]>>: > Hi, > > In general. I can see in server logs if any query executes longer, log > shows > Long running query with information about scan count and index usage. > > But if i execute from sql client EXPLAIN ANALYZE <QUERY> which returns two > rows as per below link: > > > https://apacheignite-sql.readme.io/docs/performance-and-debugging#using-explain-statement > < > https://urldefense.com/v3/__https:/apacheignite-sql.readme.io/docs/performance-and-debugging*using-explain-statement__;Iw!!PNmPxbqrAcYR!2T0TckYHNwL5PQSafBc2_K02iBzP2a8yH5qgI6KEZvtFggKtptsQ5a5pci0jvOJ2h8sl0gFE6g$ > > > > But i dont scan count returned in this. Is there any to enable it from > ignite config? > > Thanks & Regards, > Devakumar J > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/< > https://urldefense.com/v3/__http:/apache-ignite-users.70518.x6.nabble.com/__;!!PNmPxbqrAcYR!2T0TckYHNwL5PQSafBc2_K02iBzP2a8yH5qgI6KEZvtFggKtptsQ5a5pci0jvOJ2h8tAXO9IlQ$ > > >
