[
https://issues.apache.org/jira/browse/IMPALA-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916222#comment-17916222
]
ASF subversion and git services commented on IMPALA-13658:
----------------------------------------------------------
Commit 4a645105f920979759e75e136ffc6156fd268266 in impala's branch
refs/heads/master from Michael Smith
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=4a645105f ]
IMPALA-13658: Enable tuple caching aggregates
Enables tuple caching on aggregates directly above scan nodes. Caching
aggregates requires that their children are also eligible for caching,
so this excludes aggregates above an exchange, union, or hash join.
Testing:
- Adds Planner tests for different aggregate cases to confirm they have
stable tuple cache keys and are valid for caching.
- Adds custom cluster tests that cached aggregates are used, and can be
re-used in slightly different statements.
Change-Id: I9bd13c2813c90d23eb3a70f98068fdcdab97a885
Reviewed-on: http://gerrit.cloudera.org:8080/22322
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Cache aggregate results below exchange
> --------------------------------------
>
> Key: IMPALA-13658
> URL: https://issues.apache.org/jira/browse/IMPALA-13658
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Major
> Fix For: Impala 4.5.0
>
>
> Enable intermediate result caching for AGGREGATE results as long as it
> doesn't contain an exchange.
> In most aggregate cases, there is an initial aggregate, then an exchange and
> a FINALIZE aggregate. We only expect to cache the initial aggregate, as we
> don't support caching results above an exchange.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
