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

Python AfterProcessingTime triggers result in additional delay at each GBK

Details

    • Bug
    • Status: Open
    • P3
    • Resolution: Unresolved
    • None
    • None
    • sdk-py-core
    • None

    Description

      See thread discussing it: https://lists.apache.org/thread.html/rd1b59fead3927b8769514f65fa66c051f80f68a6115dae356e86302c%40%3Cdev.beam.apache.org%3E

      The solution is to switch to match Java and have "AfterSynchronizedProcessingTime" but also to allow a runner to ignore that trigger and do whatever it wants.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              kenn Kenneth Knowles
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 3h 20m
                  3h 20m