You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 17:55:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Kenneth Knowles updated BEAM-868:
---------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> 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: P3
>              Labels: 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)