[ https://issues.apache.org/jira/browse/BEAM-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17549084#comment-17549084 ]
Danny McCormick commented on BEAM-11017: ---------------------------------------- This issue has been migrated to https://github.com/apache/beam/issues/20692 > Timer with dataflow runner can be set multiple times (dataflow runner) > ---------------------------------------------------------------------- > > Key: BEAM-11017 > URL: https://issues.apache.org/jira/browse/BEAM-11017 > Project: Beam > Issue Type: Bug > Components: runner-dataflow > Affects Versions: 2.22.0, 2.23.0, 2.24.0 > Reporter: Jan Riede > Priority: P1 > > 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. -- This message was sent by Atlassian Jira (v8.20.7#820007)