[
https://issues.apache.org/jira/browse/CALCITE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402901#comment-17402901
]
Julian Hyde commented on CALCITE-4748:
--------------------------------------
Until now, we have assumed that grouping sets are unique in Aggregate. How do
you know that your change doesn't break anyone?
If you are going to make grouping sets non-unique in Aggregate, then the fix
that was made in CALCITE-1824 is no longer necessary, and you should remove it.
> If there are duplicate GROUPING SETS, Calcite should return duplicate rows
> --------------------------------------------------------------------------
>
> Key: CALCITE-4748
> URL: https://issues.apache.org/jira/browse/CALCITE-4748
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.27.0
> Reporter: duan xiong
> Assignee: duan xiong
> Priority: Critical
>
> When run SQL1:
> {code:java}
> select prod_id from foodmart.sales_fact_1997 as s group by grouping
> sets(prod_id,prod_id){code}
> and SQL2:
> {code:java}
> select prod_id from foodmart.sales_fact_1997 as s group by grouping
> sets(prod_id){code}
> get the SAME result. This is wrong. SQL1 return result's number = SQL2 return
> result*2 number
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
