[
https://issues.apache.org/jira/browse/FLINK-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133031#comment-16133031
]
Jark Wu commented on FLINK-7471:
--------------------------------
Hi [~fhueske], I think [~sunjincheng121] mean that retraction for over
aggregates is an optimization in most cases but not all cases. For example,
min/max with retraction needs to store all records of the group in the
min/max's accumulator. It's hard to say the overload of retraction mode (store
all records) is certainly less than non-retraction mode (compute all records of
a group). That's why the over window can support non-retract AGG. The over
window mode (retract/non-retract) is depends on whether all the aggregates
implement the retract methods. And the retract method is not mandatory anymore
for over window.
> Improve bounded OVER support non-retract method AGG
> ---------------------------------------------------
>
> Key: FLINK-7471
> URL: https://issues.apache.org/jira/browse/FLINK-7471
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: sunjincheng
> Assignee: sunjincheng
>
> Currently BOUNDED OVER WINDOW only support have {{retract}} method AGG. In
> this JIRA. will add non-retract method support.
> What do you think? [~fhueske]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
