becketqin commented on issue #25485:
URL: https://github.com/apache/beam/issues/25485#issuecomment-1436508424
I dug a little bit more into the code. It looks that one potential issue
here is that `GroupByKey` actually applies to its output `PCollection` a
Trigger whose behavior is different from the `WindowingStrategy` of its input
`PCollection`.
In this case, the input of the first sum has a `WindowingStrategy` with
trigger of `AfterProcessingTime.pastFirstElementInPane().plusDelayOf(1
second)`, but the output `WindowingStrategy` is
`AfterSynchronizedProcessingTime.pastFirstElementInPane()`, so the delay was
ignored and not passed on to the second sum. This is caused by the
`getContinuationTrigger(List<Trigger> continuationTriggers)` implementation in
`AfterProcessingTime`, which always returns
`AfterSynchronizedProcessingTime.ofFirstElement()` and ignores the
`TimestampTransform`. Due to this, the second sum in this test does not honor
the trigger delay.
Is this expected or is it a bug?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
