ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4524) Indexes usage in SQL functions like min/max
Date Fri, 31 Mar 2017 13:28:41 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 <sergey.chugunov@gmail.com>
Date:   2017-03-31T09:32:04Z

    IndexingSpi test fixed

commit 261a5eeafdc9f7db8446ca6b58896c9a249ee618
Author: Sergey Chugunov <sergey.chugunov@gmail.com>
Date:   2017-03-31T10:53:26Z

    H2CompareBigQueryTest configuration issue (probably introduced with merge) fixed

commit 5b5c838060e8d0c9160a82caa3b9052d0f5e8d69
Author: Dmitriy Govorukhin <dgovorukhin@gridgain.com>
Date:   2017-03-31T12:01:39Z

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

commit c7f8c4682cccf17d9fad007e2152422e545aeaa8
Author: Dmitriy Govorukhin <dgovorukhin@gridgain.com>
Date:   2017-03-31T12:13:42Z

    ignite-3477-master minor update import

commit 3f49b18ef85009893ed9f22ac0368263cb417e05
Author: Dmitriy Govorukhin <dgovorukhin@gridgain.com>
Date:   2017-03-31T12:14:40Z

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

commit 5cf3f05d476407e7a8bcdacb516f8d826c968300
Author: Ilya Lantukh <ilantukh@gridgain.com>
Date:   2017-03-31T12:35:44Z

    Fixed GridCacheAtomicEntryProcessorDeploymentSelfTest.

commit f701c6af2198ea22ef59f57063e053db7536f3cd
Author: Ilya Lantukh <ilantukh@gridgain.com>
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 <skalashnikov@gridgain.com>
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)

Mime
View raw message