Re: SQL management and monitoring improvements

Yuri, Do you have any ideas in mind? On Mon, Nov 12, 2018 at 1:25 PM Юрий wrote: > Hi Alex, > > Thanks for the ideas! It will be useful. > However, from my side, Oracle like syntax looks excess. Will be good if > someone else say opinion opinion about syntax. > > Igniters, what do you think

Re: SQL management and monitoring improvements

Hi Alex, Thanks for the ideas! It will be useful. However, from my side, Oracle like syntax looks excess. Will be good if someone else say opinion opinion about syntax. Igniters, what do you think which syntax of Ignite management via SQL will be prefer? пт, 9 нояб. 2018 г. в 0:37, Alex

Re: SQL management and monitoring improvements

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

Re: SQL management and monitoring improvements

Denis, I mentioned about it, may be it's not so clear now. I'll try add more explanation about it into IEP. It should be some SQL systems views and JMX interfaces. Deeper details will be covered in a tasks during more detailed analyze. Thanks for your feedback. чт, 8 нояб. 2018 г. в 0:06,

Re: SQL management and monitoring improvements

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

SQL management and monitoring improvements

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 . What do you think about it? May be do you