You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2023/01/11 07:12:03 UTC

[jira] [Updated] (IGNITE-18464) Sql. Colocated sort aggregates need to compose a plans with additional sort if no appropriate index is available.

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

Evgeny Stanilovsky updated IGNITE-18464:
----------------------------------------
    Description: 
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}
Seems map aggregate not require sorted input or smth about it.

  was:
For now requests like :
{noformat}
SELECT COUNT(DISTINCT val0) FROM test{noformat}
Can`t be planned through SortAggregates, ("ColocatedHashAggregateConverterRule", "MapReduceHashAggregateConverterRule") - need to be disabled. 

But seems we need to obtain smth like :
{noformat}
IgniteProject
  IgniteReduceSortAggregate
    IgniteExchange
      IgniteMapSortAggregate
        IgniteSort <-?
          IgniteTableScan{noformat}
Seems map aggregate not require sorted input or smth about it.


> 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
>
> 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}
> Seems map aggregate not require sorted input or smth about it.



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