[
https://issues.apache.org/jira/browse/CALCITE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640194#comment-14640194
]
Julian Hyde edited comment on CALCITE-751 at 7/24/15 9:18 AM:
--------------------------------------------------------------
Fixed in
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/cf7a7a97.
In this iteration, it is not safe to use the extended rule (that can handle
aggregate functions) in the Volcano planner, only in the Hep planner. The
extended rule requires metadata that can handle cyclic relational expressions
(to be fixed in CALCITE-794).
was (Author: julianhyde):
Fixed in
http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/cf7a7a97.
In this iteration, it is not safe to use the extended rule (that can handle
aggregate functions) in the Volcano planner, only in the Hep planner. The
extended rule requires metadata that can handle cyclic relational expressions
(to be fixed in CALCITE-794).
> Push aggregate with aggregate functions through join
> ----------------------------------------------------
>
> Key: CALCITE-751
> URL: https://issues.apache.org/jira/browse/CALCITE-751
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Fix For: 1.4.0-incubating
>
>
> AggregateJoinTransposeRule currently only fires if the Aggregate has no
> aggregate functions. We need to lift that limitation.
> Aggregate functions should be split, e.g. COUNT becomes SUM of COUNT. Some
> aggregate functions cannot be split, e.g. distinct-count.
> Add a new interface to SqlAggFunction to allow it to declare the split policy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
