[
https://issues.apache.org/jira/browse/FLINK-11520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-11520:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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 / Task
> Reporter: Elias Levy
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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
(v8.20.1#820001)
