You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2018/11/19 16:12:00 UTC
[jira] [Resolved] (BEAM-867) Support set/delete of timers by ID in
Flink runner
[ https://issues.apache.org/jira/browse/BEAM-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maximilian Michels resolved BEAM-867.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.9.0
Setting/deleting has been implemented via {{a3a96bc121d877acd28b55475b4ace8aec6e7949}}.
This was also required for correctly scoping timers per key/window such that each invocation of {{set}} resets Flink's internal timer to the current timer.
> Support set/delete of timers by ID in Flink runner
> --------------------------------------------------
>
> Key: BEAM-867
> URL: https://issues.apache.org/jira/browse/BEAM-867
> Project: Beam
> Issue Type: New Feature
> Components: runner-flink
> Reporter: Kenneth Knowles
> Assignee: Maximilian Michels
> Priority: Major
> Fix For: 2.9.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This is a prerequisite for full support of BEAM-27, and related to BEAM-35.
> My current understanding is that this might be actually removed from Flink itself, and needs implementation in terms of state. It might be reasonable to just remove deletion from Beam; it is just a nice-to-have for user experience IMO, and perhaps a performance help for certain runners.
> (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
(v7.6.3#76005)