[
https://issues.apache.org/jira/browse/BEAM-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131916#comment-17131916
]
Beam JIRA Bot commented on BEAM-2487:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Give a option to ignore the timer that is larger than END_OF_GLOBAL_WINDOW
> --------------------------------------------------------------------------
>
> Key: BEAM-2487
> URL: https://issues.apache.org/jira/browse/BEAM-2487
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Jingsong Lee
> Priority: P2
> Labels: stale-P2
>
> Event time can not reach END_OF_GLOBAL_WINDOW in unbounded world. (Except for
> testing)
> But Flink runner will set some timers when user set a StatefulPardo/GBK with
> GlobalWindow. Flink maintains timers in PriorityQueue on the Java Heap. There
> is a bad performance when the number of keys is very much.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
