You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2022/01/11 19:09:00 UTC
[jira] [Commented] (FLINK-25614) Let LocalWindowAggregate be chained with upstream
[ https://issues.apache.org/jira/browse/FLINK-25614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17473102#comment-17473102 ]
Martijn Visser commented on FLINK-25614:
----------------------------------------
[~jingzhang] What do you think?
> Let LocalWindowAggregate be chained with upstream
> -------------------------------------------------
>
> Key: FLINK-25614
> URL: https://issues.apache.org/jira/browse/FLINK-25614
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Runtime
> Affects Versions: 1.14.2
> Reporter: Q Kang
> Priority: Minor
> Labels: pull-request-available
>
> When enabling two-phase aggregation (local-global) strategy for Window TVF, the physical plan is shown as follows:
> {code:java}
> TableSourceScan -> Calc -> WatermarkAssigner -> Calc
> ||
> || [FORWARD]
> ||
> LocalWindowAggregate
> ||
> || [HASH]
> ||
> GlobalWindowAggregate
> ||
> ||
> ...{code}
> We can let the `LocalWindowAggregate` node be chained with upstream operators in order to improve efficiency, just like the non-windowing counterpart `LocalGroupAggregate`.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)