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:58:02 UTC

[jira] [Updated] (BEAM-11194) Add timer family id support in KeyedTimerData

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

Kenneth Knowles updated BEAM-11194:
-----------------------------------
    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.

> Add timer family id support in KeyedTimerData
> ---------------------------------------------
>
>                 Key: BEAM-11194
>                 URL: https://issues.apache.org/jira/browse/BEAM-11194
>             Project: Beam
>          Issue Type: Task
>          Components: runner-samza
>            Reporter: Ke Wu
>            Assignee: Ke Wu
>            Priority: P2
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Timer family id is not being encoded in KeyedTimerDataCoder, which means Samza cannot use this feature at all.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)