[
https://issues.apache.org/jira/browse/FLINK-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-12295:
-----------------------------------
Labels: auto-unassigned pull-request-available (was: auto-unassigned)
> avoid to call retractExpressions method of max/min function in retractable
> aggregate code-gen
> ---------------------------------------------------------------------------------------------
>
> Key: FLINK-12295
> URL: https://issues.apache.org/jira/browse/FLINK-12295
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Runtime
> Reporter: godfrey he
> Assignee: Jingsong Lee
> Priority: Major
> Labels: auto-unassigned, pull-request-available
> Fix For: 1.14.0
>
>
> after {{FlinkRelMdModifiedMonotonicity}} introduced, a max/min function whose
> result value is modified increasing/decreasing could ignore retraction
> message. We could choose regular max/min function instead of retract max/min
> function in code-gen. Currently, this requires the regular max/min function
> must implements {{retractExpressions}} method and do not throw any
> exceptions. A better approach is the retractable aggregate operator does not
> call {{retractExpressions}} method for max/min function.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
