[
https://issues.apache.org/jira/browse/BEAM-5265?focusedWorklogId=196607&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-196607
]
ASF GitHub Bot logged work on BEAM-5265:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Feb/19 18:50
Start Date: 09/Feb/19 18:50
Worklog Time Spent: 10m
Work Description: stale[bot] commented on pull request #6305: [BEAM-5265]
Use currentProcessingTime() for onTime with processing time domain
URL: https://github.com/apache/beam/pull/6305
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 196607)
Time Spent: 4h 20m (was: 4h 10m)
> Can not test Timer with processing time domain
> ----------------------------------------------
>
> Key: BEAM-5265
> URL: https://issues.apache.org/jira/browse/BEAM-5265
> Project: Beam
> Issue Type: Bug
> Components: runner-core, runner-direct
> Reporter: Jozef Vilcek
> Assignee: Jozef Vilcek
> Priority: Major
> Labels: triaged
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> I have a stateful DoFn which has a timer on PROCESSING_TIME domain. While
> writing tests, I noticed that it does not react to `advanceProcessingTime()`
> on tests stream. Problem seems to be here:
> [https://github.com/apache/beam/blob/master/runners/core-java/src/main/java/org/apache/beam/runners/core/SimpleDoFnRunner.java#L260]
> I can only tell that patching this place works for direct runner tests. Not
> sure about broader impact on other runners since it is in `runner-core`
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
