[
https://issues.apache.org/jira/browse/IGNITE-10621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718673#comment-16718673
]
Vladimir Ozerov edited comment on IGNITE-10621 at 12/12/18 9:28 AM:
--------------------------------------------------------------------
[~jooger],
I would propose to split this task into several independent tasks:
# Ability to track original queries on reducer (currently neither DML, nor DDL
works correctly in {{master}})
# Implement local and distributed views for this info
# Meanwhile - discuss how to expose running query fragments (e.g. map queries,
DML queries of different flavors, etc) to user. Honestly, I have no clear
understanding on how it should look like. May be we should take general
approach - e.g. it may be a kind of plans where every step is exposed as a
separate line like in other databases. But may be we should start with very
specific scenario instead. E.g. show only currently running map queries.
There is no ideal solution. I would propose to continue this discussion on the
dev list.
was (Author: vozerov):
[~jooger],
I would propose to split this task into several independent tasks:
# Ability to track original queries on reducer (currently neither DML, nor DDL
works correctly in {{master}})
# Implement local and distributed views for this info
# Meanwhile - discuss how to expose running query fragments (e.g. map queries,
DML queries of different flavors, etc) to user. Honestly, I have no clear
understanding on how it should look like. May be we should take general
approach - e.g. it may be a kind of plans where every step is exposed as a
separate line like in other databases. But may be we should start with very
specific scenario instead. E.g. show only currently running map queries.
There is not ideal solution. I would propose to continue this discussion on the
dev list.
> 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)
