ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yury Gerzhedovich (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-10347) Expose system SQL view for running queries
Date Mon, 21 Jan 2019 15:53:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747931#comment-16747931
] 

Yury Gerzhedovich edited comment on IGNITE-10347 at 1/21/19 3:52 PM:
---------------------------------------------------------------------

[~vozerov],
 1. Ok, agree.
 2. I'm not sure that for SQL view we need to add word 'SQL', my thoughts that when we use
SQL view then by default it should contains SQL related information. Any way I modified
name of the view.

3. I had a little thought on this and decided that will be useful information because user
couldn't know node id, e.g. use thin jdbc driver. Ok, removed the field.

4. implemented and ready to review as separated ticket - https://issues.apache.org/jira/browse/IGNITE-10160 

5. Why we shouldn't reduce number of queries rows as earlier as possible? In this case we
potentially save memory and CPU time. Currently removed it, but let's discuss.

6. We use query id as HEX because it have more shortly than decimal value and it was discussed
on dev list. Which clarity should have user for query id? It just an id. Let's discuss.

7. Added


was (Author: jooger):
[~vozerov],
 1. Ok, agree.
 2. I'm not sure that for SQL view we need to add word 'SQL', my thoughts that when we use
SQL view then by default it should contains SQL related information. Any way I modify name
of the view.

3. I had a little thought on this and decided that will be useful information because user
couldn't know node id, e.g. use thin jdbc driver. Ok, removed the field.

4. implemented and ready to review as separated ticket - https://issues.apache.org/jira/browse/IGNITE-10160 

5. Why we shouldn't reduce number of queries rows as earlier as possible? In this case we
potentially save memory and CPU time. Currently removed it, but let's discuss.

6. We use query id as HEX because it have more shortly than decimal value and it was discussed
on dev list. Which clarity should have user for query id? It just an id. Let's discuss.

7. Added

> Expose system SQL view for running queries
> ------------------------------------------
>
>                 Key: IGNITE-10347
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10347
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Yury Gerzhedovich
>            Assignee: Yury Gerzhedovich
>            Priority: Major
>              Labels: iep-29, sql
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Need to  expose system SQL view to provide list of running queries. Proposed name
is *running_queries* with following columns: query_id, node_id, sql, schema_name, duration.
> Where,
> query_id - cluster unique id of query with format \{node_order_id}
> {X}
> {node_qry_cntr}, both node_order_id and node_qry_cntr encoded to HEX. X - 'X' letter
used as separator.
> node_id - id of node where query was started
> sql - sql command
> schema_name - SQL schema name
> duration - time in ms from start of execution of query
>  
> The view should contains all kind of running queries from RunningQueryManager on local
node



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message