[
https://issues.apache.org/jira/browse/FLINK-8690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394068#comment-16394068
]
Rong Rong commented on FLINK-8690:
----------------------------------
You are right. Haven't thought about that. I will verify the plan cost. However
I am less worry about the DataStream side as the Calcite rule will generate 2
operations that requires state backend while using MapView will generate only
1. My worry is on DataSet, as per my initial implementation of splitting
FlinkLogicalAggregate into 2, both of them ignores the plan generated by
{{AggregateExpandDistinctAggregatesRule}}
> Update logical rule set to generate FlinkLogicalAggregate explicitly allow
> distinct agg on DataStream
> -----------------------------------------------------------------------------------------------------
>
> Key: FLINK-8690
> URL: https://issues.apache.org/jira/browse/FLINK-8690
> Project: Flink
> Issue Type: Sub-task
> Reporter: Rong Rong
> Assignee: Rong Rong
> Priority: Major
>
> Currently, *FlinkLogicalAggregate / FlinkLogicalWindowAggregate* does not
> allow distinct aggregate.
> We are proposing to reuse distinct aggregate codegen work designed for
> *FlinkLogicalOverAggregate*, to support unbounded distinct aggregation on
> datastream as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
