[jira] [Updated] (IGNITE-10311) SQL: Create system view with query co-location plans

2020-07-03 Thread Aleksey Plekhanov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Plekhanov updated IGNITE-10311:
---
Fix Version/s: (was: 2.9)

> SQL: Create system view with query co-location plans
> 
>
> Key: IGNITE-10311
> URL: https://issues.apache.org/jira/browse/IGNITE-10311
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>  Labels: iep-29
>
> It is very important to understand model of distributed execution for certain 
> queries for performance tuning. Let's create a syhstem view which will 
> iterate over cached two-step queries and print their plans in table form. 
> Approximate structure (very raw):
> {code}
> CREATE VIEW sql_query_plan (
> plan_id, // Unique plan ID (node ID + unique local ID)
> sql, // Plain text
> sql_hash. // May be more convenient that query_id
> flags // Same query with different flags may result in different plans
> )
> CREATE VIEW sql_query_plan_fragments (
> plan_id, // Same plan ID
> order, // Together with plan_id it forms PK
> action, // What is this - "reduce", "skip reduce", "map", etc. (may be we 
> will need multiple columns)
> sql, // SQL of the fragment (if applicable)
> )
> {code}
> Next user may list cached plans, select interesting, and query plan fragments 
> view. 
> We need to analyze other vendors to better understand what to show in views.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (IGNITE-10311) SQL: Create system view with query co-location plans

2019-10-08 Thread Maxim Muzafarov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-10311:
-
Fix Version/s: (was: 2.8)
   2.9

> SQL: Create system view with query co-location plans
> 
>
> Key: IGNITE-10311
> URL: https://issues.apache.org/jira/browse/IGNITE-10311
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>  Labels: iep-29
> Fix For: 2.9
>
>
> It is very important to understand model of distributed execution for certain 
> queries for performance tuning. Let's create a syhstem view which will 
> iterate over cached two-step queries and print their plans in table form. 
> Approximate structure (very raw):
> {code}
> CREATE VIEW sql_query_plan (
> plan_id, // Unique plan ID (node ID + unique local ID)
> sql, // Plain text
> sql_hash. // May be more convenient that query_id
> flags // Same query with different flags may result in different plans
> )
> CREATE VIEW sql_query_plan_fragments (
> plan_id, // Same plan ID
> order, // Together with plan_id it forms PK
> action, // What is this - "reduce", "skip reduce", "map", etc. (may be we 
> will need multiple columns)
> sql, // SQL of the fragment (if applicable)
> )
> {code}
> Next user may list cached plans, select interesting, and query plan fragments 
> view. 
> We need to analyze other vendors to better understand what to show in views.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (IGNITE-10311) SQL: Create system view with query co-location plans

2019-01-29 Thread Vladimir Ozerov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-10311:
-
Labels: iep-29  (was: iep-24)

> SQL: Create system view with query co-location plans
> 
>
> Key: IGNITE-10311
> URL: https://issues.apache.org/jira/browse/IGNITE-10311
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>  Labels: iep-29
> Fix For: 2.8
>
>
> It is very important to understand model of distributed execution for certain 
> queries for performance tuning. Let's create a syhstem view which will 
> iterate over cached two-step queries and print their plans in table form. 
> Approximate structure (very raw):
> {code}
> CREATE VIEW sql_query_plan (
> plan_id, // Unique plan ID (node ID + unique local ID)
> sql, // Plain text
> sql_hash. // May be more convenient that query_id
> flags // Same query with different flags may result in different plans
> )
> CREATE VIEW sql_query_plan_fragments (
> plan_id, // Same plan ID
> order, // Together with plan_id it forms PK
> action, // What is this - "reduce", "skip reduce", "map", etc. (may be we 
> will need multiple columns)
> sql, // SQL of the fragment (if applicable)
> )
> {code}
> Next user may list cached plans, select interesting, and query plan fragments 
> view. 
> We need to analyze other vendors to better understand what to show in views.



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

[jira] [Updated] (IGNITE-10311) SQL: Create system view with query co-location plans

2018-11-16 Thread Vladimir Ozerov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-10311:
-
Labels: iep-24  (was: )

> SQL: Create system view with query co-location plans
> 
>
> Key: IGNITE-10311
> URL: https://issues.apache.org/jira/browse/IGNITE-10311
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>  Labels: iep-24
> Fix For: 2.8
>
>
> It is very important to understand model of distributed execution for certain 
> queries for performance tuning. Let's create a syhstem view which will 
> iterate over cached two-step queries and print their plans in table form. 
> Approximate structure (very raw):
> {code}
> CREATE VIEW sql_query_plan (
> plan_id, // Unique plan ID (node ID + unique local ID)
> sql, // Plain text
> sql_hash. // May be more convenient that query_id
> flags // Same query with different flags may result in different plans
> )
> CREATE VIEW sql_query_plan_fragments (
> plan_id, // Same plan ID
> order, // Together with plan_id it forms PK
> action, // What is this - "reduce", "skip reduce", "map", etc. (may be we 
> will need multiple columns)
> sql, // SQL of the fragment (if applicable)
> )
> {code}
> Next user may list cached plans, select interesting, and query plan fragments 
> view. 
> We need to analyze other vendors to better understand what to show in views.



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