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

Posted to issues-all@impala.apache.org by "Steve Carlin (Jira)" <ji...@apache.org> on 2026/04/20 15:50:00 UTC

[jira] [Updated] (IMPALA-13451) Calcite planner does not take advantage of the hash partition of previous aggregates

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

Steve Carlin updated IMPALA-13451:
----------------------------------
        Parent:     (was: IMPALA-12871)
    Issue Type: Improvement  (was: Sub-task)

> Calcite planner does not take advantage of the hash partition of previous aggregates
> ------------------------------------------------------------------------------------
>
>                 Key: IMPALA-13451
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13451
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: Impala 4.5.0
>            Reporter: Joe McDonnell
>            Assignee: Steve Carlin
>            Priority: Major
>
> In [IMPALA-13197|http://issues.apache.org/jira/browse/IMPALA-13197], we added support for analytic functions to the Calcite planner. The implementation passes empty lists to the second two parameters of AnalyticPlanner. That disables a small optimization which can avoid exchanges when the input is already hash partitioned in a compatible way:
> [https://github.com/apache/impala/commit/0b3124ab35402f1ab8141e8ffcca28a5a481c81e]
> This is a tracking Jira just so we don't forget about this difference.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org