On Tue, Feb 13, 2018 at 8:22 PM, Nikolay Izhikov
wrote:
> 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?
>
I
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
Hello, Denis.
> Or is it just a separate task?
Yes, it is a separate task.
I propose to have a different method for each type of long running user task:
* continuous queries
* compute tasks
* compute jobs
В Вт, 13/02/2018 в 17:23 -0800, Denis Magda пишет:
> Sounds like a right addition to our
Sounds like a right addition to our metrics APIs.
However, I’m not sure how this part is related to continuous queries:
> * List of running compute tasks for node:
>* node ID task started from.
>* task class name.
>* other task parameters.
>* creation timestamp (?)
>* st
Nikolay, how about regular SQL queries?
On Tue, Feb 13, 2018 at 6:31 AM, Nikolay Izhikov
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 exten
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
