[
https://issues.apache.org/jira/browse/FLINK-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029534#comment-15029534
]
ASF GitHub Bot commented on FLINK-3087:
---------------------------------------
GitHub user ChengXiangLi opened a pull request:
https://github.com/apache/flink/pull/1414
[FLINK-3087] [Table-API] support multi count in aggregation
The `Literal(1)` is used as the IntermediateField of `Count` aggregation,
so multi `Count` looks the same in `ExpandAggregations`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ChengXiangLi/flink countAggregation
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1414.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1414
----
commit d83690c521b22e7af339353ed1b06b3d199e9c42
Author: chengxiang li <[email protected]>
Date: 2015-11-27T06:46:29Z
[FLINK-3087] [Table-API] support multi count in aggregation
----
> 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)
