You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kostas Kloudas (JIRA)" <ji...@apache.org> on 2016/05/25 15:55:12 UTC

[jira] [Assigned] (FLINK-3714) Add Support for "Allowed Lateness"

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

Kostas Kloudas reassigned FLINK-3714:
-------------------------------------

    Assignee: Kostas Kloudas

> Add Support for "Allowed Lateness"
> ----------------------------------
>
>                 Key: FLINK-3714
>                 URL: https://issues.apache.org/jira/browse/FLINK-3714
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Streaming
>            Reporter: Aljoscha Krettek
>            Assignee: Kostas Kloudas
>
> As mentioned in https://docs.google.com/document/d/1Xp-YBf87vLTduYSivgqWVEMjYUmkA-hyb4muX3KRl08/edit# we should add support for an allowed lateness setting.
> This includes several things:
>  - API for setting allowed lateness
>  - Dropping of late elements 
>  - Garbage collection of event-time windows 
> Lateness only makes sense for event-time windows. So we also have to figure out what the API for this should look like and especially what should happen with the "stream-time characteristic" switch. For example in this:
> {code}
> env.setStreamTimeCharacteristic(ProcessingTime)
> ...
> DataStream in = ...
> result = in
>   .keyBy()
>   .timeWindow()
>   .allowedLateness()
>   .apply()
> {code}
> I think the setting can be silently ignored when doing processing-time windowing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)