You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Liya Fan (Jira)" <ji...@apache.org> on 2020/10/19 02:07:00 UTC

[jira] [Updated] (CALCITE-4342) More aggregate functions should be marked as splittable and ignore distinct optionality

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

Liya Fan updated CALCITE-4342:
------------------------------
    Summary: More aggregate functions should be marked as splittable and ignore distinct optionality  (was: More aggregate functions should be marked as splittable and duplicate-insensitive)

> More aggregate functions should be marked as splittable and ignore distinct optionality
> ---------------------------------------------------------------------------------------
>
>                 Key: CALCITE-4342
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4342
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>            Reporter: Liya Fan
>            Assignee: Liya Fan
>            Priority: Major
>
> As discussed in the mailing list, there are more aggregate functions (e.g. SINGLE_VALUE, ANY_VALUE) that can be classified as splittable and duplicate-insensitive. We need to tell the optimizer explicitly about this, so more optimizations can be applied in various scenarios. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)