[
https://issues.apache.org/jira/browse/BEAM-3354?focusedWorklogId=458889&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-458889
]
ASF GitHub Bot logged work on BEAM-3354:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jul/20 19:44
Start Date: 14/Jul/20 19:44
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #4341:
URL: https://github.com/apache/beam/pull/4341#issuecomment-658376373
@ffDante can you file a Jira describing what you have encountered?
https://issues.apache.org/jira/secure/CreateIssue!default.jspa
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 458889)
Time Spent: 20m (was: 10m)
> Timer setRelative() does not reset previously set timer.
> --------------------------------------------------------
>
> Key: BEAM-3354
> URL: https://issues.apache.org/jira/browse/BEAM-3354
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Batkhuyag Batsaikhan
> Assignee: Batkhuyag Batsaikhan
> Priority: P2
> Fix For: 2.3.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When running a pipeline with Timer on direct runner as mentioned in
> https://beam.apache.org/blog/2017/08/28/timely-processing.html, multiple
> calls to setRelative() is starting new timers rather than resetting. (set()
> method is resetting the timer correctly)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
