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/17 11:51:00 UTC
[jira] [Closed] (FLINK-12170) Add support for generating optimized
logical plan for Over aggregate
[ https://issues.apache.org/jira/browse/FLINK-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Young closed FLINK-12170.
------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
fixed in e42f6b52cf43a1a3aaac37d3f8c66e647be63ece
> Add support for generating optimized logical plan for Over aggregate
> --------------------------------------------------------------------
>
> Key: FLINK-12170
> URL: https://issues.apache.org/jira/browse/FLINK-12170
> 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 aims to generate optimized plan for Over aggregate queries on both Batch and Stream, e.g.
> {code:sql}
> SELECT a, b, c, RANK() OVER (PARTITION BY b ORDER BY c) FROM MyTable
> {code}
> currently, Stream requires all over aggregate functions must be computed on the same window, e.g.
> {code:sql}
> SELECT c,
> COUNT(a) OVER (PARTITION BY c ORDER BY proctime RANGE UNBOUNDED PRECEDING),
> SUM(a) OVER (PARTITION BY b ORDER BY proctime RANGE UNBOUNDED PRECEDING)
> from MyTable
> {code}
> the above sql is not supported because the partition keys are different.
> Batch does not have such limitation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)