You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jeyhun Karimov (JIRA)" <ji...@apache.org> on 2016/01/29 13:00:44 UTC
[jira] [Commented] (FLINK-3089) OperatorState timeout
[ https://issues.apache.org/jira/browse/FLINK-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123391#comment-15123391 ]
Jeyhun Karimov commented on FLINK-3089:
---------------------------------------
If nobody works on this issue, I would like to give a try.
> OperatorState timeout
> ---------------------
>
> Key: FLINK-3089
> URL: https://issues.apache.org/jira/browse/FLINK-3089
> Project: Flink
> Issue Type: New Feature
> Reporter: Niels Basjes
>
> In some usecases (webanalytics) there is a need to have a state per visitor on a website (i.e. keyBy(sessionid) ).
> At some point the visitor simply leaves and no longer creates new events (so a special 'end of session' event will not occur).
> The only way to determine that a visitor has left is by choosing a timeout, like "After 30 minutes no events we consider the visitor 'gone'".
> Only after this (chosen) timeout has expired should we discard this state.
> In the Trigger part of Windows we can set a timer and close/discard this kind of information. But that introduces the buffering effect of the window (which in some scenarios is unwanted).
> What I would like is to be able to set a timeout on a specific OperatorState value which I can update afterwards.
> This makes it possible to create a map function that assigns the right value and that discards the state automatically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)