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

Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2019/02/28 16:17:00 UTC

[jira] [Updated] (FLINK-11520) Triggers should be provided the window state

     [ https://issues.apache.org/jira/browse/FLINK-11520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Metzger updated FLINK-11520:
-----------------------------------
    Component/s: Runtime / Operators

> Triggers should be provided the window state
> --------------------------------------------
>
>                 Key: FLINK-11520
>                 URL: https://issues.apache.org/jira/browse/FLINK-11520
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Operators
>            Reporter: Elias Levy
>            Priority: Major
>
> Some triggers may require access to the window state to perform their job.  Consider a window computing a count using an aggregate function.  It may be desired to fire the window when the count is 1 and then at the end of the window.  The early firing can provide feedback to external systems that a key has been observed, while waiting for the final count.
> The same problem can be observed in org.apache.flink.streaming.api.windowing.triggers.CountTrigger, which must maintain an internal count instead of being able to make use of the window state.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)