Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-3379 Refactor TimestampExtractor
  3. FLINK-3401

AscendingTimestampExtractor should not fail on order violation

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.10.1
    • 1.0.0
    • None
    • None

    Description

      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.

      Attachments

        Activity

          People

            sewen Stephan Ewen
            sewen Stephan Ewen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: