You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/04 19:01:11 UTC
[GitHub] [beam] damccorm opened a new issue, #20692: Timer with dataflow runner can be set multiple times (dataflow runner)
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: github-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] damccorm closed issue #20692: Timer with dataflow runner can be set multiple times (dataflow runner)
Posted by GitBox <gi...@apache.org>.
damccorm closed issue #20692: Timer with dataflow runner can be set multiple times (dataflow runner)
URL: https://github.com/apache/beam/issues/20692
--
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: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] kennknowles commented on issue #20692: Timer with dataflow runner can be set multiple times (dataflow runner)
Posted by GitBox <gi...@apache.org>.
kennknowles commented on issue #20692:
URL: https://github.com/apache/beam/issues/20692#issuecomment-1246007953
I believe this has been fixed. Can you confirm @reuvenlax? I believe you were in the loop on the fix.
--
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: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] reuvenlax commented on issue #20692: Timer with dataflow runner can be set multiple times (dataflow runner)
Posted by GitBox <gi...@apache.org>.
reuvenlax commented on issue #20692:
URL: https://github.com/apache/beam/issues/20692#issuecomment-1246274678
I believe this was caused by the output-timestamp bug, and should now be fixed.
--
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: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org