ignite-issues mailing list archives

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

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

Sergey Kalashnikov edited comment on IGNITE-4524 at 3/31/17 1:32 PM:
---------------------------------------------------------------------

Implemented. However, we need to fix H2 issue with index selection in order to fully fix this.
The changes are based on ignite-3477-master branch.


was (Author: skalashnikov):
Implemented. However, we need to fix H2 issue with index selection in order to fully fix this.

> 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