[
https://issues.apache.org/jira/browse/IGNITE-10621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714703#comment-16714703
]
ASF GitHub Bot commented on IGNITE-10621:
-----------------------------------------
GitHub user ygerzhedovich opened a pull request:
https://github.com/apache/ignite/pull/5620
IGNITE-10621
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10621
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5620.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5620
----
commit 6f8dd8726b7bf0039a038491f384c346222d37be
Author: Yury Gerzhedovich <ygerzhedovich@...>
Date: 2018-12-10T12:57:39Z
IGNITE-10621: Start work on tracking all running queries
----
> Track all running queries
> -------------------------
>
> Key: IGNITE-10621
> URL: https://issues.apache.org/jira/browse/IGNITE-10621
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Yury Gerzhedovich
> Priority: Major
> Labels: iep-29
> Fix For: 2.8
>
>
> As of now Ignite track running queries in few places and use
> GridRunningQueryInfo to keep information about each of running query.
> Unfortunately we track not all running queries. Need to track all DML and
> Select queries. Be able to distinguish user initial queries and system
> auxiliary queries, e.g. map/reduce queries or select for DML operations. Also
> there is single point to track all running queries.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
