Dmitriy I thought about those type of tasks that require custom user code to be executed inside Ignite.
Your suggestion make sense for me also. Let's include SQL queries. Should we include ScanQuery, TextQuery to this API? В Вт, 13/02/2018 в 13:27 -0800, Dmitriy Setrakyan пишет: > Nikolay, how about regular SQL queries? > > On Tue, Feb 13, 2018 at 6:31 AM, Nikolay Izhikov <nizhi...@apache.org> > wrote: > > > Hello, Igniters. > > > > We have some requests from users [1] to have ability to get list of all > > running continuous queries. > > I propose to implement such ability. > > > > To implement it we have to extend our JMX beans to provide the following > > information: > > > > * List of continuous queries for cache: > > * local listener node. > > * listener class name. > > * routine ID. > > * other CQ parameters > > * creation timestamp (?) > > > > * List of running compute tasks for node: > > * node ID task started from. > > * task class name. > > * other task parameters. > > * creation timestamp (?) > > * start timestamp (?) > > > > * List of running jobs for node: > > * node ID task started from. > > * task class name. > > * other job parameters. > > * creation timestamp (?) > > * start timestamp (?) > > > > I'm planning to file tickets to implement these features. > > So, please, write if you have any objections. > > > > [1] http://apache-ignite-developers.2346864.n4.nabble. > > com/Re-List-of-running-Continuous-queries-or-CacheEntryListener-per-cache- > > or-node-tp25526.html
signature.asc
Description: This is a digitally signed message part
