[
https://issues.apache.org/jira/browse/BEAM-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16707568#comment-16707568
]
Luke Cwik commented on BEAM-6157:
---------------------------------
Not blocking, just good to understand since there is likely a bug here that is
being worked around.
> SplittableParDoViaKeyedWorkItems sets another timer when receiving
> ProcessContinuation#STOP
> -------------------------------------------------------------------------------------------
>
> Key: BEAM-6157
> URL: https://issues.apache.org/jira/browse/BEAM-6157
> Project: Beam
> Issue Type: Bug
> Components: runner-core, runner-direct
> Reporter: Luke Cwik
> Assignee: Scott Wegner
> Priority: Major
>
> [HBaseIOTest#testReadingKeyRangeMiddleSDF|https://github.com/apache/beam/blob/b06b8e5df5738e7dc3620f67134da67a4a806758/sdks/java/io/hbase/src/test/java/org/apache/beam/sdk/io/hbase/HBaseIOTest.java#L326]
> consistently fails if SplittableParDoViaKeyedWorkItems sets the wake-up time
> to be the resume time when receiving a ProcessContinuation#STOP
> Why are we setting another timer to execute after STOP?
> Also, why is the direct runner failing to make progress with the timer if it
> is set in the past relative to the current process time?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
