[
https://issues.apache.org/jira/browse/FLINK-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855397#comment-15855397
]
ASF GitHub Bot commented on FLINK-3475:
---------------------------------------
Github user docete commented on the issue:
https://github.com/apache/flink/pull/3111
Agree. If we have more than one distinct agg with groupings, do the
partition first and reuse the subsets would improve the performance.
Could we merge this PR first and create another JIRA to track the grouping
cases?
We need a workaround to support distinct aggs ASAP.
> DISTINCT aggregate function support for SQL queries
> ---------------------------------------------------
>
> Key: FLINK-3475
> URL: https://issues.apache.org/jira/browse/FLINK-3475
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Chengxiang Li
> Assignee: Zhenghua Gao
>
> DISTINCT aggregate function may be able to reuse the aggregate function
> instead of separate implementation, and let Flink runtime take care of
> duplicate records.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
