[jira] [Closed] (BEAM-6329) State for portable timers can interfere with user state

["Maximilian Michels (JIRA)" <ji...@apache.org>]

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

Maximilian Michels closed BEAM-6329.
------------------------------------
    Resolution: Fixed

> State for portable timers can interfere with user state
> -------------------------------------------------------
>
>                 Key: BEAM-6329
>                 URL: https://issues.apache.org/jira/browse/BEAM-6329
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>    Affects Versions: 2.9.0
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Critical
>              Labels: portability-flink
>             Fix For: 2.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current active key needs to be set on Flink's state backend to support deleting pending timers on timer registration or firing. A keyed map for pending timers is necessary because Flink only allows deleting/resetting timers by their original time, not by their ids.
> Setting the current active key can interfere with accessing user-defined state, but can also interfere when a timer is set at the same time that a timer fires. In cases with a key initialized by the state requests, this would have caused pending timers to be associated with the wrong key which would have led to problems deleting / resetting them.
> Related to: BEAM-4681 BEAM-867



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)