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

Flink Jira Bot updated FLINK-8470:
----------------------------------
    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.


> DelayTrigger and DelayAndCountTrigger in Flink Streaming Window API
> -------------------------------------------------------------------
>
>                 Key: FLINK-8470
>                 URL: https://issues.apache.org/jira/browse/FLINK-8470
>             Project: Flink
>          Issue Type: New Feature
>          Components: API / DataStream
>    Affects Versions: 2.0.0
>            Reporter: Vijay Kansal
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In Flink streaming API, we do not have any in-built window trigger(s) 
> available for the below use cases:
>  1. DelayTrigger: Window function should trigger in case the 1st element 
> belonging to this window arrived more than maxDelay(ms) before the current 
> processing time.
> 2. DelayAndCountTrigger: Window function should trigger in case the 1st 
> element belonging to this window arrived more than maxDelay(ms) before the 
> current processing time or there are more than maxCount elements in the 
> window.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to