You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2016/12/12 18:57:58 UTC

[jira] [Resolved] (BEAM-35) Remove timer multiplexing and give timers identifiers

     [ https://issues.apache.org/jira/browse/BEAM-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles resolved BEAM-35.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.4.0-incubating

> Remove timer multiplexing and give timers identifiers
> -----------------------------------------------------
>
>                 Key: BEAM-35
>                 URL: https://issues.apache.org/jira/browse/BEAM-35
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-core
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>             Fix For: 0.4.0-incubating
>
>
> Today, timers set by the runner core of the SDK are identified by timestamp, so multiple timers for the same time result in only one backend timer. This is runner-specific and obsolete, and makes it unsafe to support timer deletion because backend timers have no real owner. User-facing timers will require explicit identifiers anyhow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)