[
https://issues.apache.org/jira/browse/CALCITE-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005070#comment-16005070
]
Julian Hyde edited comment on CALCITE-1781 at 5/10/17 5:26 PM:
---------------------------------------------------------------
It already worked; added some tests in
http://git-wip-us.apache.org/repos/asf/calcite/commit/5ee895d3.
was (Author: julianhyde):
It already worked; adde some tests in
http://git-wip-us.apache.org/repos/asf/calcite/commit/5ee895d3.
> Allow expression in CUBE and ROLLUP
> -----------------------------------
>
> Key: CALCITE-1781
> URL: https://issues.apache.org/jira/browse/CALCITE-1781
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Fix For: 1.13.0
>
>
> Currently we only allow columns as arguments to CUBE and ROLLUP operators,
> whereas we allow expressions in the GROUP BY clause. This change would also
> allow expressions as arguments to CUBE and ROLLUP. Example:
> {code}
> // the following are valid, and will remain valid
> select deptno from emp group by deptno;
> select deptno +1 from emp group by deptno + 1;
> select deptno from emp group by cube(deptno);
> select deptno from emp group by rollup(deptno);
> // the following are currently invalid, but would be valid
> select deptno +1 from emp group by cube(deptno + 1, empno - 1);
> select deptno +1 from emp group by rollup(deptno + 1, empno - 1);
> {code}
> Note that as of CALCITE-1306, and with {{SqlConformance.isGroupByOrdinal}}
> enabled, {{select deptno from emp group by cube(1)}} should be valid because
> {{1}} is interpreted as an ordinal in the SELECT clause, not an expression.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
