Yuri, I think it will be useful if we extend in future management via SQL tool to cover not only queries but also other parts of Ignite (for example: for canceling tasks, for killing transactions, activation/deactivation, baseline topology change, etc.).
Maybe, in this case, we should use a common prefix for such management commands (like Oracle do: "ALTER SYSTEM ...")? Something like: ALTER GRID KILL QUERY ... [ON NODE ...] ALTER GRID KILL TRANSACTION ... [ON NODE ...] ALTER GRID ACTIVATE etc. What do you think about it? чт, 8 нояб. 2018 г. в 0:06, Denis Magda <[email protected]>: > Yuri, > > That's an excellent idea, thank you for driving it. > > What is not explained is how to leverage from all that stat. For instance, > how can I know a total number of SELECTs, or a total number of SELECTs > happened yesterday for specific data sets. Do believe that it's feasible > and just not covered. > > -- > Denis > > > > On Wed, Nov 7, 2018 at 2:01 AM Юрий <[email protected]> wrote: > > > Hi Igniters! > > > > I think we can improve Ignite management and monitoring instruments > related > > to SQL. > > I've prepared draft of IEP-29: SQL management and monitoring > > < > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-29%3A+SQL+management+and+monitoring > > > > > . > > > > What do you think about it? May be do you have some additional > suggestions? > > > > > > -- > > Живи с улыбкой! :D > > >
