[jira] [Updated] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases

2018-03-19 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4510:

Labels: sql-performance  (was: performance)

> SQL: co-located query may calculate target partition in advance in some cases
> -
>
> Key: IGNITE-4510
> URL: https://issues.apache.org/jira/browse/IGNITE-4510
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Priority: Major
>  Labels: sql-performance
>
> Consider the following SQL query with {{distributedJoins=false}}:
> {code}
> SELECT ... 
> FROM Employee e
> INNER JOIN Department d on d.id = e.dept_id
> WHERE e.dept_id = ?
> {code}
> If {{dept_id}} is affinity key, and this should be certainly so in case of 
> non-colocated joins (otherwise query will return incorrect result), then we 
> can do the following:
> 1) Determine partition for this affinity key.
> 2) Send query execution request to this partition only.
> Same technique can be applied to {{WHERE e.dept_id IN (?, ...)}} case.



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

[jira] [Updated] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases

2017-08-22 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4510:

Fix Version/s: (was: 2.2)

> SQL: co-located query may calculate target partition in advance in some cases
> -
>
> Key: IGNITE-4510
> URL: https://issues.apache.org/jira/browse/IGNITE-4510
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>  Labels: performance
>
> Consider the following SQL query with {{distributedJoins=false}}:
> {code}
> SELECT ... 
> FROM Employee e
> INNER JOIN Department d on d.id = e.dept_id
> WHERE e.dept_id = ?
> {code}
> If {{dept_id}} is affinity key, and this should be certainly so in case of 
> non-colocated joins (otherwise query will return incorrect result), then we 
> can do the following:
> 1) Determine partition for this affinity key.
> 2) Send query execution request to this partition only.
> Same technique can be applied to {{WHERE e.dept_id IN (?, ...)}} case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases

2017-08-16 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4510:

Labels: performance  (was: important performance sql)

> SQL: co-located query may calculate target partition in advance in some cases
> -
>
> Key: IGNITE-4510
> URL: https://issues.apache.org/jira/browse/IGNITE-4510
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>  Labels: performance
> Fix For: 2.2
>
>
> Consider the following SQL query with {{distributedJoins=false}}:
> {code}
> SELECT ... 
> FROM Employee e
> INNER JOIN Department d on d.id = e.dept_id
> WHERE e.dept_id = ?
> {code}
> If {{dept_id}} is affinity key, and this should be certainly so in case of 
> non-colocated joins (otherwise query will return incorrect result), then we 
> can do the following:
> 1) Determine partition for this affinity key.
> 2) Send query execution request to this partition only.
> Same technique can be applied to {{WHERE e.dept_id IN (?, ...)}} case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases

2017-05-22 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4510:

Fix Version/s: 2.2

> SQL: co-located query may calculate target partition in advance in some cases
> -
>
> Key: IGNITE-4510
> URL: https://issues.apache.org/jira/browse/IGNITE-4510
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>  Labels: important, performance, sql
> Fix For: 2.2
>
>
> Consider the following SQL query with {{distributedJoins=false}}:
> {code}
> SELECT ... 
> FROM Employee e
> INNER JOIN Department d on d.id = e.dept_id
> WHERE e.dept_id = ?
> {code}
> If {{dept_id}} is affinity key, and this should be certainly so in case of 
> non-colocated joins (otherwise query will return incorrect result), then we 
> can do the following:
> 1) Determine partition for this affinity key.
> 2) Send query execution request to this partition only.
> Same technique can be applied to {{WHERE e.dept_id IN (?, ...)}} case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases

2017-05-22 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4510:

Labels: important performance sql  (was: performance sql)

> SQL: co-located query may calculate target partition in advance in some cases
> -
>
> Key: IGNITE-4510
> URL: https://issues.apache.org/jira/browse/IGNITE-4510
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>  Labels: important, performance, sql
> Fix For: 2.2
>
>
> Consider the following SQL query with {{distributedJoins=false}}:
> {code}
> SELECT ... 
> FROM Employee e
> INNER JOIN Department d on d.id = e.dept_id
> WHERE e.dept_id = ?
> {code}
> If {{dept_id}} is affinity key, and this should be certainly so in case of 
> non-colocated joins (otherwise query will return incorrect result), then we 
> can do the following:
> 1) Determine partition for this affinity key.
> 2) Send query execution request to this partition only.
> Same technique can be applied to {{WHERE e.dept_id IN (?, ...)}} case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases

2017-02-03 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4510:

Fix Version/s: (was: 2.1)

> SQL: co-located query may calculate target partition in advance in some cases
> -
>
> Key: IGNITE-4510
> URL: https://issues.apache.org/jira/browse/IGNITE-4510
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>  Labels: performance, sql
>
> Consider the following SQL query with {{distributedJoins=false}}:
> {code}
> SELECT ... 
> FROM Employee e
> INNER JOIN Department d on d.id = e.dept_id
> WHERE e.dept_id = ?
> {code}
> If {{dept_id}} is affinity key, and this should be certainly so in case of 
> non-colocated joins (otherwise query will return incorrect result), then we 
> can do the following:
> 1) Determine partition for this affinity key.
> 2) Send query execution request to this partition only.
> Same technique can be applied to {{WHERE e.dept_id IN (?, ...)}} case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases

2017-02-03 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4510:

Fix Version/s: (was: 2.0)
   2.1

> SQL: co-located query may calculate target partition in advance in some cases
> -
>
> Key: IGNITE-4510
> URL: https://issues.apache.org/jira/browse/IGNITE-4510
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>  Labels: performance, sql
> Fix For: 2.1
>
>
> Consider the following SQL query with {{distributedJoins=false}}:
> {code}
> SELECT ... 
> FROM Employee e
> INNER JOIN Department d on d.id = e.dept_id
> WHERE e.dept_id = ?
> {code}
> If {{dept_id}} is affinity key, and this should be certainly so in case of 
> non-colocated joins (otherwise query will return incorrect result), then we 
> can do the following:
> 1) Determine partition for this affinity key.
> 2) Send query execution request to this partition only.
> Same technique can be applied to {{WHERE e.dept_id IN (?, ...)}} case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4510) SQL: co-located query may calculate target partition in advance in some cases

2016-12-29 Thread Vladimir Ozerov (JIRA) 

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

Vladimir Ozerov updated IGNITE-4510:

Labels: performance sql  (was: sql)

> SQL: co-located query may calculate target partition in advance in some cases
> -
>
> Key: IGNITE-4510
> URL: https://issues.apache.org/jira/browse/IGNITE-4510
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>  Labels: performance, sql
> Fix For: 2.0
>
>
> Consider the following SQL query with {{distributedJoins=false}}:
> {code}
> SELECT ... 
> FROM Employee e
> INNER JOIN Department d on d.id = e.dept_id
> WHERE e.dept_id = ?
> {code}
> If {{dept_id}} is affinity key, and this should be certainly so in case of 
> non-colocated joins (otherwise query will return incorrect result), then we 
> can do the following:
> 1) Determine partition for this affinity key.
> 2) Send query execution request to this partition only.
> Same technique can be applied to {{WHERE e.dept_id IN (?, ...)}} case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)