IEP-29 IGNITE-10165 Gather query stats and expose interfaces to access it

[Dmitrii Ryabov]

Hello, Igniters,

I want to do IGNITE-10165 (Gather query stats and expose interfaces to
access it) [1], if you don't mind.

Yury, Vladimir, did you planned something about statistics implementation?

Also, can you point out in which sessions should be available option to
turn on/off stats gathering? This also mentioned in the IEP-29 [2] and
IGNITE-10166 [3].

[1] https://issues.apache.org/jira/browse/IGNITE-10165
[2]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
[3] https://issues.apache.org/jira/browse/IGNITE-10166

[Vladimir Ozerov]

Hi Dmitry,

AFAIK this is already work in progress by Yuriy. IEP-29 has a number of
tickets, but they should be implemented one by one, not in parallel,
because they heavily depend on each other. First we need to build
infrastructure for running queries (see topic "proposed design for thin
client SQL management and monitoring (view running queries and kill it)"),
then restore and redesign query history (it is broken now), then expose
them through views and implement KILL command.. Every step would require
certain recactoring in indexing module. I would suggest you to pick
something else to avoid clashes and merge conflicts.

Vladimir.

On Tue, Dec 4, 2018 at 12:15 PM Dmitrii Ryabov <[hidden email]>
wrote:

> Hello, Igniters,
>
> I want to do IGNITE-10165 (Gather query stats and expose interfaces to
> access it) [1], if you don't mind.
>
> Yury, Vladimir, did you planned something about statistics implementation?
>
> Also, can you point out in which sessions should be available option to
> turn on/off stats gathering? This also mentioned in the IEP-29 [2] and
> IGNITE-10166 [3].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-10165
> [2]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring
> [3] https://issues.apache.org/jira/browse/IGNITE-10166
>