Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-14244

Processing time timers should use outputTimestamp rather than input watermark for their timestamp

Details

    • Bug
    • Status: Resolved
    • P1
    • Resolution: Fixed
    • None
    • 2.39.0
    • runner-core, sdk-java-core
    • None

    Description

      Currently processing time timers ignore the outputTimestamp and instead use the input watermark at the time they fire.  This is wrong because the input watermark can have advanced arbitrarily far past the actual output timestamp when it fires.

      The correct behavior should be to instead use the outputTimestamp the timer was configured to fire with.

      Attachments

        Issue Links

          Activity

            People

              SteveNiemitz Steve Niemitz
              SteveNiemitz Steve Niemitz
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 9h 50m
                  9h 50m