[
https://issues.apache.org/jira/browse/FLINK-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834186#comment-15834186
]
ASF GitHub Bot commented on FLINK-5450:
---------------------------------------
Github user kl0u commented on the issue:
https://github.com/apache/flink/pull/3134
@rmetzger I see. Then my PR fixes it, as the problem was that when
retrieving timers, we were first putting them in the temporary list in the
`initializeState` and the re-register them with the `TimerService` in the
`open()`. When re-registering we were not checking if there were any timers to
re-register before printing the message. That is why the message was logged all
the time.
> WindowOperator logs about "re-registering state from an older Flink version"
> even though its not a restored window
> ------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-5450
> URL: https://issues.apache.org/jira/browse/FLINK-5450
> Project: Flink
> Issue Type: Bug
> Components: Windowing Operators
> Affects Versions: 1.2.0
> Reporter: Robert Metzger
> Assignee: Kostas Kloudas
>
> While testing the RC0 of Flink 1.2, I stumbled across this log message
> {code}
> 15:42:02,855 INFO
> org.apache.flink.streaming.api.operators.AbstractStreamOperator -
> WindowOperator (taskIdx=WindowOperator) re-registering state from an older
> Flink version.
> {code}
> My WindowOperator is not restored, so I find this log message a bit
> misleading.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
