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

AfterProcessingTime trigger not reliable; only fires on double numbers' event

Details

    • Bug
    • Status: Resolved
    • P2
    • Resolution: Duplicate
    • 2.6.0
    • Not applicable
    • runner-flink
    • None

    Description

      we use following statement in sql to configure the window trigger:

       sometimes it doesn't fire but the data is recorded in the window. and event come afterwards, the trigger fires with all the data together.

      I uploaded a video of screenshot on google drive. It will show the behavior of this.

      https://drive.google.com/file/d/1wOo2s4ifAdwdAglbzOb0jEYZszsQPFjx/view?usp=sharing

       

      org.apache.beam.sdk.transforms.windowing.Window.configure()
          .triggering(org.apache.beam.sdk.transforms.windowing.AfterWatermark.pastEndOfWindow()
              .withEarlyFirings(org.apache.beam.sdk.transforms.windowing.AfterProcessingTime.pastFirstElementInPane().plusDelayOf(org.joda.time.Duration.millis(0)))
              .withLateFirings(org.apache.beam.sdk.transforms.windowing.AfterProcessingTime.pastFirstElementInPane().plusDelayOf(org.joda.time.Duration.millis(20000))))
      .withAllowedLateness(org.joda.time.Duration.millis(3600000), org.apache.beam.sdk.transforms.windowing.Window.ClosingBehavior.valueOf("FIRE_IF_NON_EMPTY"))
          .withOnTimeBehavior(org.apache.beam.sdk.transforms.windowing.Window.OnTimeBehavior.valueOf("FIRE_IF_NON_EMPTY")).accumulatingFiredPanes()
      

      Attachments

        Issue Links

          Activity

            People

              mxm Maximilian Michels
              jacshen Jin Shen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: