[
https://issues.apache.org/jira/browse/IGNITE-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18208:
---------------------------------------
Description:
Currently, planner tests for aggregates doesn't have any logical structure. As
a result it hard to say which queries should be processed by 2-phase aggregate,
and which by colocated aggregates.
Let's restructure the tests in order to get answer on following questions:
* which queries should be processed by colocated aggregates
* which queries should be processed by 2-phase aggregates
* which queries should leverage the sorted aggregates
Let's analyze test coverage tests and create separate ticket to extend coverage
in case it require.
was:
Currently, planner tests for aggregates doesn't have any logical structure. As
a result it hard to say which queries should be processed by 2-phase aggregate,
and which by colocated aggregates.
Let's restructure the tests in order to get answer on following questions:
* which queries should be processed by colocated aggregates
* which queries should be processed by 2-phase aggregates
* which queries should leverage the sorted aggregates
> Sql. Restructuring of the planner tests for aggregates
> -------------------------------------------------------
>
> Key: IGNITE-18208
> URL: https://issues.apache.org/jira/browse/IGNITE-18208
> Project: Ignite
> Issue Type: Improvement
> Reporter: Konstantin Orlov
> Priority: Major
>
> Currently, planner tests for aggregates doesn't have any logical structure.
> As a result it hard to say which queries should be processed by 2-phase
> aggregate, and which by colocated aggregates.
> Let's restructure the tests in order to get answer on following questions:
> * which queries should be processed by colocated aggregates
> * which queries should be processed by 2-phase aggregates
> * which queries should leverage the sorted aggregates
> Let's analyze test coverage tests and create separate ticket to extend
> coverage in case it require.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)