[ 
https://issues.apache.org/jira/browse/CALCITE-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376042#comment-17376042
 ] 

Julian Hyde commented on CALCITE-4665:
--------------------------------------

[~nobigo], That test case and RelNode looks good. Can you submit a PR to add 
it? Add a comment to {{example5}} noting that groupKeys contain unused columns.

However the SQL is invalid, because {{JOB}} is in the {{SELECT}} clause but is 
not in any of the {{GROUPING SETS}}. We need to fix a bug in RelToSqlConverter. 
I think the solution is to generate the "superset" grouping set, then filter it 
out:
{code:sql}
 GROUP BY GROUPING SETS(("EMPNO", "ENAME", "JOB"),("EMPNO", "ENAME"), "EMPNO")
HAVING GROUPING_ID("EMPNO", "ENAME", "JOB") != 7{code}
 
Also modify the javadoc of one of the {{RelBuilder.aggregate}} methods, and of 
{{Aggregate}}'s constructor that {{groupKey}} may be a superset of the union of 
the {{groupKeys}}.

> When group by are same as sub-query, grouping sets are missing
> --------------------------------------------------------------
>
>                 Key: CALCITE-4665
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4665
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.22.0
>            Reporter: xiejiajun
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.28.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
>  UT:
> {code:java}
>         builder.scan("EMP")
>             .aggregate(builder.groupKey(0, 1, 7),
>                 builder.aggregateCall(SqlStdOperatorTable.COUNT,
>                     builder.field("JOB")).as("job_num"))
>             .aggregate(
>                 builder.groupKey(ImmutableBitSet.of(0, 1, 2),
>                     (Iterable<ImmutableBitSet>)
>                         ImmutableList.of(ImmutableBitSet.of(0, 1))))
>             // GROUP BY 0,1,2 GROUPING SETS((0, 1))
>             .build();
> {code}
> Before I fixed it, you can see groupings set are missing because 
> LogicalProject.
> {code:java}
> LogicalProject(EMPNO=[$0], ENAME=[$1], DEPTNO=[$2])
>   LogicalAggregate(group=[{0, 1, 7}], job_num=[COUNT($2)])
>     LogicalTableScan(table=[[scott, EMP]]){code}
> After I fixed it,  groupings set will be saved.
> {code:java}
> LogicalAggregate(group=[{0, 1, 2}], groups=[[{0, 1}]])
>  LogicalAggregate(group=[{0, 1, 7}], job_num=[COUNT($2)])
>    LogicalTableScan(table=[[scott, EMP]]{code}
>   Although the user will not write such SQL directly, it does happen after 
> the logic is complicated, and the user will be confused about the wrong data.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to