flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3401) AscendingTimestampExtractor should not fail on order violation
Date Wed, 17 Feb 2016 13:16:18 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150478#comment-15150478
] 

ASF GitHub Bot commented on FLINK-3401:
---------------------------------------

Github user StephanEwen commented on the pull request:

    https://github.com/apache/flink/pull/1647#issuecomment-185199372
  
    Manually merged in e08d7a6f30f8e3b845ff33d4266fbd4fad4bec63


> 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)

Mime
View raw message