[jira] [Updated] (IGNITE-13919) Calcite integration. Single group aggregates
[
https://issues.apache.org/jira/browse/IGNITE-13919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-13919:
Labels: calcite (was: calcite calcite3-required)
> Calcite integration. Single group aggregates
>
>
> Key: IGNITE-13919
> URL: https://issues.apache.org/jira/browse/IGNITE-13919
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Minor
> Labels: calcite
> Fix For: 2.15
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Investigate the optimization for single group aggregates,
> e.g.: {{SELECT FROM }}
> Now the hash based aggregates are used for this case.
> We can obtain a little performance improvement.
> Also the special cases (e.g.: {{SELECT COUNT() FROM }})
> may be optimized to use table/cache size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13919) Calcite integration. Single group aggregates
[
https://issues.apache.org/jira/browse/IGNITE-13919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-13919:
---
Labels: calcite calcite3-required (was: calcite2-required
calcite3-required)
> Calcite integration. Single group aggregates
>
>
> Key: IGNITE-13919
> URL: https://issues.apache.org/jira/browse/IGNITE-13919
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Aleksey Plekhanov
>Priority: Minor
> Labels: calcite, calcite3-required
> Fix For: 2.15
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Investigate the optimization for single group aggregates,
> e.g.: {{SELECT FROM }}
> Now the hash based aggregates are used for this case.
> We can obtain a little performance improvement.
> Also the special cases (e.g.: {{SELECT COUNT() FROM }})
> may be optimized to use table/cache size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-13919) Calcite integration. Single group aggregates
[
https://issues.apache.org/jira/browse/IGNITE-13919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-13919:
--
Priority: Minor (was: Major)
> Calcite integration. Single group aggregates
>
>
> Key: IGNITE-13919
> URL: https://issues.apache.org/jira/browse/IGNITE-13919
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Minor
> Labels: calcite2-required, calcite3-required
>
> Investigate the optimization for single group aggregates,
> e.g.: {{SELECT FROM }}
> Now the hash based aggregates are used for this case.
> We can obtain a little performance improvement.
> Also the special cases (e.g.: {{SELECT COUNT() FROM }})
> may be optimized to use table/cache size.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13919) Calcite integration. Single group aggregates
[
https://issues.apache.org/jira/browse/IGNITE-13919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-13919:
---
Labels: calcite2-required calcite3-required (was: )
> Calcite integration. Single group aggregates
>
>
> Key: IGNITE-13919
> URL: https://issues.apache.org/jira/browse/IGNITE-13919
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Taras Ledkov
>Priority: Major
> Labels: calcite2-required, calcite3-required
>
> Investigate the optimization for single group aggregates,
> e.g.: {{SELECT FROM }}
> Now the hash based aggregates are used for this case.
> We can obtain a little performance improvement.
> Also the special cases (e.g.: {{SELECT COUNT() FROM }})
> may be optimized to use table/cache size.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
