You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kurt Young (JIRA)" <ji...@apache.org> on 2019/04/11 06:13:00 UTC
[jira] [Closed] (FLINK-12098) Add support for generating optimized
logical plan for simple group aggregate on stream
[ https://issues.apache.org/jira/browse/FLINK-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Young closed FLINK-12098.
------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
fixed in 517a04f1cbe74d10340b1cb17eb2b4a1b1b11195
> Add support for generating optimized logical plan for simple group aggregate on stream
> --------------------------------------------------------------------------------------
>
> Key: FLINK-12098
> URL: https://issues.apache.org/jira/browse/FLINK-12098
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Planner
> Reporter: godfrey he
> Assignee: godfrey he
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This issue only involves simple stream group aggregate, complex group aggregate(including GROUP SETS and DISTINCT) will also be finished in new issue.
> A logical aggregate will be converted to StreamExecGroupAggregate, and a StreamExecGroupAggregate will be written to two-stage aggregates (StreamExecLocalGroupAggregate and StreamExecGlobalGroupAggregate) if mini-batch is enabled and all aggregate functions are mergeable.
> Retraction rules will also be ported, because multiple level aggregates will produce retraction message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)