Hi,
Yes, it can be specified in your Spring configuration file as follows:
...
Thanks,
Slava.
пн, 16 июл. 2018 г. в 19:39, ApacheUser :
> Hi Slava,
> Sorry to get into this thread,I have similar problem to control long
> running
> SQLs. I want timeout SQLs running more than 500ms.
Hi Slava,
Sorry to get into this thread,I have similar problem to control long running
SQLs. I want timeout SQLs running more than 500ms.
I sthere any way to set etLongQueryWarningTimeout() in CONFIG File?
Appreciate your response.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabb
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 follo
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/
