[
https://issues.apache.org/jira/browse/FLINK-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012216#comment-16012216
]
Fabian Hueske commented on FLINK-6598:
--------------------------------------
I think this is valid SQL syntax that can be easily supported and don't see a
reason why we should not allow this.
It works the same way in any relational database, so I would not expect users
to be surprised or confused.
In fact, Calcite translates certain DISTINCT clauses into GROUP BY without
aggregations (this is how it works in batch / DataSet).
> Fix `DataStreamGroupAggregateRule`and `DataStreamGroupWindowAggregateRule`
> matches error.
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-6598
> URL: https://issues.apache.org/jira/browse/FLINK-6598
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Reporter: sunjincheng
> Assignee: sunjincheng
> Fix For: 1.3.0
>
>
> Changes as follows:
> 1. Add {{!agg.getAggCallList.isEmpty}} condition for
> {{DataStreamGroupWindowAggregateRule}} and {{DataStreamGroupAggregateRule}}.
> 2. Remove useless param {{rowRelDataType}} of {{DataStreamGroupAggregate}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
