Hello Dave, I am afraid that there is no such possibility out of the box. The simple workaround that I can imagine is using IgniteConfiguration#setLongQueryWarningTimeout() method and set 1ms for example. In that case, every SQL request that spends more than 1ms will be printed in the log as follows: [2018-01-04 06:32:38,230][WARN ] [IgniteH2Indexing] Query execution is too long [time=3518 ms, sql='the execution plan of your SQL query will be printed here"
I think you can modify the code of IgniteH2Indexing#executeSqlQueryWithTimer for debugging purposes, and print out an execution plan always. Thanks, S. чт, 12 июл. 2018 г. в 16:07, Dave Harvey <[email protected]>: > Is there a simple way inside Ignite to get a log of all SQL Queries against > the cluster, either in the debug logs or elsewhere ? This is not a easy > question to phase in a way that Google will find a useful answer. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
