[
https://issues.apache.org/jira/browse/BEAM-12742?focusedWorklogId=637495&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-637495
]
ASF GitHub Bot logged work on BEAM-12742:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Aug/21 18:40
Start Date: 12/Aug/21 18:40
Worklog Time Spent: 10m
Work Description: kw2542 commented on a change in pull request #15322:
URL: https://github.com/apache/beam/pull/15322#discussion_r687994742
##########
File path:
sdks/java/core/src/test/java/org/apache/beam/sdk/transforms/ParDoTest.java
##########
@@ -4670,7 +4670,7 @@ public void onTimer(
}
@Test
- @Category(NeedsRunner.class)
+ @Category({NeedsRunner.class, UsesTimersInParDo.class,
UsesTestStream.class})
Review comment:
Good point, this is what I would like to understand the common practice
in beam.
`UsesTestStreamWithProcessingTime` is a subtype of `UsesTestStream`, based
on JUnit documentation, tests marked as `UsesTestStreamWithProcessingTime` is
also part of `UsesTestStream` but not the other way around.
Therefore, if a test is marked as `UsesTestStreamWithProcessingTime`, then
marking it with `UsesTestStream` does not effectively change how it behaves
since it transiently belongs to `UsesTestStream` category as well.
However, I do agree that having both annotations here are clearer and more
readable and there does not seem to have cons to have both annotations.
What are your suggestions here?
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 637495)
Time Spent: 1h 50m (was: 1h 40m)
> Samza Runner does not properly delete modified timer
> ----------------------------------------------------
>
> Key: BEAM-12742
> URL: https://issues.apache.org/jira/browse/BEAM-12742
> Project: Beam
> Issue Type: Bug
> Components: runner-samza
> Reporter: Ke Wu
> Assignee: Ke Wu
> Priority: P2
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> SamzaTimerInternalsFactory:267
> {code:java}
> final TimerData lastTimerData =
> TimerData.of(
> timerData.getTimerId(),
> timerData.getNamespace(),
> new Instant(lastTimestamp),
> new Instant(lastTimestamp),
> timerData.getDomain());
> deleteTimer(lastTimerData, false);
> {code}
> does not properly delete old timer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
