[
https://issues.apache.org/jira/browse/CALCITE-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652441#comment-14652441
]
Julian Hyde commented on CALCITE-827:
-------------------------------------
Yes, that sounds very likely. I wrote that comment so thank me for
helping/blame me for not doing it right first time (your choice).
> ProjectToWindowRule leads to Assertion Error when multiple windows are used
> in a specific way
> ---------------------------------------------------------------------------------------------
>
> Key: CALCITE-827
> URL: https://issues.apache.org/jira/browse/CALCITE-827
> Project: Calcite
> Issue Type: Bug
> Reporter: Sean Hsuan-Yi Chu
> Assignee: Sean Hsuan-Yi Chu
>
> To reproduce this issue, add ProjectToWindowRule to the Hep Planner.
> Then, a query below would fail with an Assertion Error (type mis-match)
> {code}
> select count(*) over(partition by empno order by sal) as count1,
> count(*) over(partition by deptno order by sal) as count2,
> sum(deptno) over(partition by empno order by sal) as sum1
> from emp
> {code}
> However, if the second and third columns are swapped, then it works:
> {code}
> select count(*) over(partition by empno order by sal) as count1,
> sum(deptno) over(partition by empno order by sal) as sum1,
> count(*) over(partition by deptno order by sal) as count2
> from emp
> {code}
> Essentially, the window functions which "share the same window definition"
> should be placed consecutively in the select-list; Otherwise, the current
> linking mechanism seems having some difficulty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
