You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2016/02/17 12:27:18 UTC

[jira] [Closed] (FLINK-3401) AscendingTimestampExtractor should not fail on order violation

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

Stephan Ewen closed FLINK-3401.
-------------------------------

> AscendingTimestampExtractor should not fail on order violation
> --------------------------------------------------------------
>
>                 Key: FLINK-3401
>                 URL: https://issues.apache.org/jira/browse/FLINK-3401
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Streaming
>    Affects Versions: 0.10.1
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 1.0.0
>
>
> Currently, the {{AscendingTimestampExtractor}} fails hard when the order of timestamps is violated.
> In the spirit of "streaming jobs never fail", I propose to change the default behavior such that violations are only logged (later collected in metrics) and that hard failures have to be explicitly activated.



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