damccorm opened a new issue, #20692:
URL: https://github.com/apache/beam/issues/20692
After the update from version 2.21.0 a timer (processing-time) was not
overwritten but additionally set.
I set a timer several times e.g.:
processingTimerFamily.get("timer1").offset(Duration.standardSeconds(60)).setRelative();
for each incoming data in an unbound streaming pipeline.
According to the documentation the timer should be set back in each case.
Since the update it seems that the existing timer is not overwritten but an
additional timer (with the same timer-id) is added.
With directrunner it still works as before.
Imported from Jira
[BEAM-11017](https://issues.apache.org/jira/browse/BEAM-11017). Original Jira
may contain additional context.
Reported by: jaribo.
--
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]
