[
https://issues.apache.org/jira/browse/FLINK-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15723552#comment-15723552
]
Rohit Agarwal commented on FLINK-5247:
--------------------------------------
The existing code already had provisions to throw exceptions when
allowedLateness is set to non-zero value for processing time windows.
{code}
throw new IllegalArgumentException("Setting the allowed
lateness is only valid for event-time windows.");
{code}
I created this JIRA because that existing code was not working as intended:
https://github.com/apache/flink/pull/2929/files
Currently, if you set allowedLateness to non-zero value for processing-time
windows, flink would update allowedLateness to that value. (This probably
results in delays in window purging.)
We can make allowedLateness method a no-op for processing-time windows, I
didn't do that because looking at the existing code that didn't seem to be the
intention.
> Setting allowedLateness to a non-zero value should throw exception for
> processing-time windows
> ----------------------------------------------------------------------------------------------
>
> Key: FLINK-5247
> URL: https://issues.apache.org/jira/browse/FLINK-5247
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3
> Reporter: Rohit Agarwal
>
> Related to FLINK-3714 and FLINK-4239
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
