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

Konstantin Orlov updated IGNITE-18464:
--------------------------------------
    Fix Version/s: 3.0.0-beta2

> Sql. Colocated sort aggregates need to compose a plans with additional sort 
> if no appropriate index is available. 
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18464
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18464
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 3.0.0-beta1
>            Reporter: Evgeny Stanilovsky
>            Assignee: Evgeny Stanilovsky
>            Priority: Major
>              Labels: calcite, ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> For now requests like :
> {noformat}
> SELECT COUNT(DISTINCT val0) FROM test{noformat}
> Can`t be planned through SortAggregates, 
> ("ColocatedHashAggregateConverterRule", 
> "MapReduceHashAggregateConverterRule", "MapReduceSortAggregateConverterRule") 
> - need to be disabled. 
> Plan with raw table without any additional indexes possibly can looks like :
> {noformat}
> IgniteProject
>   IgniteColocatedSortAggregate
>     IgniteExchange
>         IgniteSort (this sort is important here)
>           IgniteTableScan{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to