You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "godfrey he (JIRA)" <ji...@apache.org> on 2019/04/23 06:53:00 UTC
[jira] [Updated] (FLINK-12295) use retract aggregate function
instead of regular aggregate function for retractable aggregate in code gen
[ https://issues.apache.org/jira/browse/FLINK-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
godfrey he updated FLINK-12295:
-------------------------------
Description: 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. (was: after {{FlinkRelMdModifiedMonotonicity}} introduced, an aggregate function whose result value is modified increasing or decreasing could ignore retraction message. We could choose regular aggregate function instead of retract aggregate function for those aggregate functions in code-gen. Currently, this requires the regular aggregate function must implements {{retractExpressions}} method and do not throw any exception. A better approach is the retractable aggregate operator does not call {{retractExpressions}} method for regular aggregate function.)
> use retract aggregate function instead of regular aggregate function for retractable aggregate in 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: godfrey he
> Priority: Major
>
> 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
(v7.6.3#76005)