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 2022/12/27 10:26:00 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:
----------------------------------------
Labels: calcite ignite-3 (was: ignite-3)
> 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
> 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") - 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)