Hi Igniters, As of now we have query statistics ( *org.apache.ignite.IgniteCache#queryMetrics*) , but it's look a little bit wrong, due to at least few reasons: 1) Duration execution it just time between start execution and return cursor to client and doesn't include all life time of query. 2) It doesn't know about multistatement queries. Such queries participate in statistics as single query without splitting. 3) API to access the statistics expose as depend on cache, however query don't have such dependency.
I want to create parallel similar realization as we already have. But it should fix all above mistakes: 1) Use new infrastructure of tracking running queries developed under IGNITE-10621 <https://issues.apache.org/jira/browse/IGNITE-10621> and update statistics when query really finished, so we will have real time of execution. 2) The new infrastructure support multistatement queries. And all part of such queries will be tracked independent each other. 3) Expose API on upper level then it placed now. Seems it should be on Ignite level. But I'm not fully sure. Old API will be marked as deprecated and could be deleted further, may be in 3.0 version. I created the corresponding JIRA ticket - IGNITE-10754 <https://issues.apache.org/jira/browse/IGNITE-10754> Please give me some recommendation for right place for expose the API to don't have misunderstanding in future. WDYT, do you have additional proposal for such deal? -- Живи с улыбкой! :D
