[
https://issues.apache.org/jira/browse/FLINK-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033620#comment-15033620
]
ASF GitHub Bot commented on FLINK-3087:
---------------------------------------
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1414#issuecomment-160956025
Ah, I see you changed it to my (wrong) suggestion. @ChengXiangLi Do you
want to change it back to your initial version (plus maybe the fix for the
naming and cleanExpr). Or should it be changed when adding support for null
values?
> Table API do not support multi count in aggregation.
> ----------------------------------------------------
>
> Key: FLINK-3087
> URL: https://issues.apache.org/jira/browse/FLINK-3087
> Project: Flink
> Issue Type: Bug
> Components: Table API
> Affects Versions: 0.10.0
> Reporter: Chengxiang Li
> Assignee: Chengxiang Li
>
> Multi {{count}} in aggregation is not supported, for example:
> {code:java}
> table.select("a.count", "b.count")
> {code}
> It's valid in grammar, besides, {{a.count}} and {{b.count}} may have
> different values actually if NULL value handling is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
