You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yue Ma (Jira)" <ji...@apache.org> on 2022/04/26 04:02:00 UTC

[jira] [Commented] (FLINK-27401) CEP supports AggregateFunction in IterativeCondition

    [ https://issues.apache.org/jira/browse/FLINK-27401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527874#comment-17527874 ] 

Yue Ma commented on FLINK-27401:
--------------------------------

hi [~nicholasjiang], I would glad to be involved in the design and implementation of this feature . Could you assgin this ticket to me ? 

> CEP supports AggregateFunction in IterativeCondition
> ----------------------------------------------------
>
>                 Key: FLINK-27401
>                 URL: https://issues.apache.org/jira/browse/FLINK-27401
>             Project: Flink
>          Issue Type: Improvement
>          Components: Library / CEP
>    Affects Versions: 1.16.0
>            Reporter: Nicholas Jiang
>            Priority: Major
>             Fix For: 1.16.0
>
>         Attachments: image-2022-04-26-11-56-07-467.png
>
>
> IterativeCondition only exposes the filter interface. For the aggregation operation in the condition, since the condition may be called multiple times in the NFA process, an event may cause the custom aggregation state in the condition to be updated multiple times, for example, filters goods with a total of more than 1000 orders in the past 10 minutes. AggregateFunction is introduced in IterativeCondition to initialize and maintain aggregation state.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)