You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:33 UTC
[jira] [Commented] (BEAM-868) Support set/delete of timers by ID in
Apex runner
[ https://issues.apache.org/jira/browse/BEAM-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174886#comment-17174886 ]
Beam JIRA Bot commented on BEAM-868:
------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> Support set/delete of timers by ID in Apex runner
> -------------------------------------------------
>
> Key: BEAM-868
> URL: https://issues.apache.org/jira/browse/BEAM-868
> Project: Beam
> Issue Type: New Feature
> Components: runner-apex
> Reporter: Kenneth Knowles
> Priority: P2
> Labels: stale-P2, stale-assigned
>
> This is a prerequisite for full support of BEAM-27, and related to BEAM-35.
> I haven't looked into what kind of work this would take.
> (Since I am filing individual tickets for each runner, generalized discussion should probably be on the dev list directly on or BEAM-35)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)