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/12 22:38:00 UTC

[jira] [Updated] (BEAM-12333) TimerFamilyId is not present in TimerKey in SamzaTimerInternalsFactory and therefore doesn't get persisted for Processing Time timers

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

Kenneth Knowles updated BEAM-12333:
-----------------------------------
    Status: Open  (was: Triage Needed)

> TimerFamilyId is not present in TimerKey in SamzaTimerInternalsFactory and therefore doesn't get persisted for Processing Time timers
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-12333
>                 URL: https://issues.apache.org/jira/browse/BEAM-12333
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-samza
>            Reporter: Ajo Thomas
>            Assignee: Ajo Thomas
>            Priority: P3
>
> `SamzaTimerInternalsFactory` stores timer state, event time and processing time timers alike, in the form of a MapState<TimerKey<K>, Long>. TimerKey, however, doesn't include the `TimerFamilyId` and is therefore not persisted. On the other hand, event time timers uses an additional time sorted set to persist the TimerData(which contains TimerFamilyId). We need to include timer family id in the TimerKey to ensure that it is persisted.



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