[jira] [Commented] (IGNITE-4524) Indexes usage in SQL functions like min/max

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4524:


Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/1749


> Indexes usage in SQL functions like min/max
> ---
>
> Key: IGNITE-4524
> URL: https://issues.apache.org/jira/browse/IGNITE-4524
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Denis Magda
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> If to execute queries like this
> {code}
> select min(id) from MyValue
> select max(id) from MyValue
> {code}
> assuming that 'id' is an indexed field then the engine will not gain from 
> this. 
> The SQL engine needs to be improved so that the indexes are used for queries 
> like the ones above.
> More details can be found in this discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/min-max-SQL-and-indexes-td13492.html



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

[jira] [Commented] (IGNITE-4524) Indexes usage in SQL functions like min/max

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-4524:


Applied review remarks. Had to re-create the branch and PR ( 
https://github.com/apache/ignite/pull/1749 )
[~sergi.vladykin], could you please have a look at the changes once again? 

> Indexes usage in SQL functions like min/max
> ---
>
> Key: IGNITE-4524
> URL: https://issues.apache.org/jira/browse/IGNITE-4524
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Denis Magda
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> If to execute queries like this
> {code}
> select min(id) from MyValue
> select max(id) from MyValue
> {code}
> assuming that 'id' is an indexed field then the engine will not gain from 
> this. 
> The SQL engine needs to be improved so that the indexes are used for queries 
> like the ones above.
> More details can be found in this discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/min-max-SQL-and-indexes-td13492.html



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

[jira] [Commented] (IGNITE-4524) Indexes usage in SQL functions like min/max

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4524:


GitHub user skalashnikov opened a pull request:

https://github.com/apache/ignite/pull/1749

IGNITE-4524: Index direct lookup for SQL MIN() and MAX()



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4524

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1749.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 #1749


commit 9fd888e30397612d9b732264da8b3e265ff27175
Author: skalashnikov 
Date:   2017-04-06T10:50:15Z

IGNITE-4524: Index direct lookup for SQL MIN() and MAX()




> Indexes usage in SQL functions like min/max
> ---
>
> Key: IGNITE-4524
> URL: https://issues.apache.org/jira/browse/IGNITE-4524
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Denis Magda
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> If to execute queries like this
> {code}
> select min(id) from MyValue
> select max(id) from MyValue
> {code}
> assuming that 'id' is an indexed field then the engine will not gain from 
> this. 
> The SQL engine needs to be improved so that the indexes are used for queries 
> like the ones above.
> More details can be found in this discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/min-max-SQL-and-indexes-td13492.html



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

[jira] [Commented] (IGNITE-4524) Indexes usage in SQL functions like min/max

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4524:


Github user skalashnikov closed the pull request at:

https://github.com/apache/ignite/pull/1717


> Indexes usage in SQL functions like min/max
> ---
>
> Key: IGNITE-4524
> URL: https://issues.apache.org/jira/browse/IGNITE-4524
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Denis Magda
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> If to execute queries like this
> {code}
> select min(id) from MyValue
> select max(id) from MyValue
> {code}
> assuming that 'id' is an indexed field then the engine will not gain from 
> this. 
> The SQL engine needs to be improved so that the indexes are used for queries 
> like the ones above.
> More details can be found in this discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/min-max-SQL-and-indexes-td13492.html



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

[jira] [Commented] (IGNITE-4524) Indexes usage in SQL functions like min/max

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4524:


GitHub user skalashnikov opened a pull request:

https://github.com/apache/ignite/pull/1717

IGNITE-4524: Index direct lookup for SQL functions MIN() and MAX()



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4524

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1717.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 #1717


commit 7ce61b7d08cb54f5355ae51657a3df37766a30b6
Author: Sergey Chugunov 
Date:   2017-03-31T09:32:04Z

IndexingSpi test fixed

commit 261a5eeafdc9f7db8446ca6b58896c9a249ee618
Author: Sergey Chugunov 
Date:   2017-03-31T10:53:26Z

H2CompareBigQueryTest configuration issue (probably introduced with merge) 
fixed

commit 5b5c838060e8d0c9160a82caa3b9052d0f5e8d69
Author: Dmitriy Govorukhin 
Date:   2017-03-31T12:01:39Z

ignite-3477-master fix (node can't s obtain write lock on stop)

commit c7f8c4682cccf17d9fad007e2152422e545aeaa8
Author: Dmitriy Govorukhin 
Date:   2017-03-31T12:13:42Z

ignite-3477-master minor update import

commit 3f49b18ef85009893ed9f22ac0368263cb417e05
Author: Dmitriy Govorukhin 
Date:   2017-03-31T12:14:40Z

Merge branch 'ignite-3477-master-apache' into ignite-3477-master

commit 5cf3f05d476407e7a8bcdacb516f8d826c968300
Author: Ilya Lantukh 
Date:   2017-03-31T12:35:44Z

Fixed GridCacheAtomicEntryProcessorDeploymentSelfTest.

commit f701c6af2198ea22ef59f57063e053db7536f3cd
Author: Ilya Lantukh 
Date:   2017-03-31T12:36:30Z

Merge branch 'ignite-3477-master' of 
https://github.com/gridgain/apache-ignite into ignite-3477-master

commit 4af9d8f99ae22687c49783e36c7bc0c1b206c342
Author: skalashnikov 
Date:   2017-03-31T13:19:05Z

IGNITE-4524: Index direct lookup for SQL functions MIN() and MAX()




> Indexes usage in SQL functions like min/max
> ---
>
> Key: IGNITE-4524
> URL: https://issues.apache.org/jira/browse/IGNITE-4524
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Denis Magda
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> If to execute queries like this
> {code}
> select min(id) from MyValue
> select max(id) from MyValue
> {code}
> assuming that 'id' is an indexed field then the engine will not gain from 
> this. 
> The SQL engine needs to be improved so that the indexes are used for queries 
> like the ones above.
> More details can be found in this discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/min-max-SQL-and-indexes-td13492.html



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

[jira] [Commented] (IGNITE-4524) Indexes usage in SQL functions like min/max

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-4524:


Found an issue in H2 while adding the tests for this one.

Here are the details:

{code}
drop table test if exists;
create table test(key int, a int, b int);
create index key_pk on test(key);
create index usr_idx on test(a, key);
explain select min(key) from test;

PLAN  
SELECT
MIN(KEY)
FROM PUBLIC.TEST
/* PUBLIC.USR_IDX */
/* direct lookup */
{code}

The index in "explain results" is wrong. It should be KEY_PK.


> Indexes usage in SQL functions like min/max
> ---
>
> Key: IGNITE-4524
> URL: https://issues.apache.org/jira/browse/IGNITE-4524
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Denis Magda
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> If to execute queries like this
> {code}
> select min(id) from MyValue
> select max(id) from MyValue
> {code}
> assuming that 'id' is an indexed field then the engine will not gain from 
> this. 
> The SQL engine needs to be improved so that the indexes are used for queries 
> like the ones above.
> More details can be found in this discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/min-max-SQL-and-indexes-td13492.html



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