[
https://issues.apache.org/jira/browse/FLINK-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219865#comment-15219865
]
Konstantin Knauf commented on FLINK-3669:
-----------------------------------------
In my opionen the 1st option is the cleanest, but I can hardly imagine a
usecase for which the 3rd option would be problem, so I think it is totally
fine. In this case ´registerProcessingTimeTimer()´ should document that the
timestamp is "ceiled" to the next interval and refer to the configuration
parameter.
> WindowOperator registers a lot of timers at StreamTask
> ------------------------------------------------------
>
> Key: FLINK-3669
> URL: https://issues.apache.org/jira/browse/FLINK-3669
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 1.0.1
> Reporter: Aljoscha Krettek
> Priority: Blocker
>
> Right now, the WindowOperator registers a timer at the StreamTask for every
> processing-time timer that a Trigger registers. We should combine several
> registered trigger timers to only register one low-level timer (timer
> coalescing).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
