[
https://issues.apache.org/jira/browse/FLINK-7731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198393#comment-16198393
]
Aljoscha Krettek commented on FLINK-7731:
-----------------------------------------
No, timers (and state) are never cleaned automatically. One might argue for
automatic cleanup, because it protects users from certain errors, but so far
Flink as followed the policy of "if you create it you must clean it up" (which
applies to state and timers).
> Trigger on GlobalWindow does not clean state completely
> -------------------------------------------------------
>
> Key: FLINK-7731
> URL: https://issues.apache.org/jira/browse/FLINK-7731
> Project: Flink
> Issue Type: Bug
> Components: Core, DataStream API
> Affects Versions: 1.3.2
> Reporter: Gerard Garcia
> Priority: Minor
>
> I have an operator that consists of:
> CoGroup Datastream -> GlobalWindow -> CustomTrigger -> Apply function
> The custom trigger fires and purges the elements after it has received the
> expected number of elements (or when a timeout fires) from one of the streams
> and the apply function merges the elements with the ones received from the
> other stream. It appears that the state of the operator grows continuously so
> it seems it never gets completely cleaned.
> There is a discussion in
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Clean-GlobalWidnow-state-td15613.html
> that suggests that it may be a bug.
> This job reproduces the issue:
> https://github.com/GerardGarcia/flink-global-window-growing-state
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
