[
https://issues.apache.org/jira/browse/FLINK-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942431#comment-14942431
]
ASF GitHub Bot commented on FLINK-2802:
---------------------------------------
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1216#issuecomment-145281934
Yes, this is a good workaround for the time being.
I think to get event time (watermarks) and cycles to work together would
require something akin to the multi-dimensional timestamps of Naiad.
> Watermark triggered operators cannot progress with cyclic flows
> ---------------------------------------------------------------
>
> Key: FLINK-2802
> URL: https://issues.apache.org/jira/browse/FLINK-2802
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Blocker
>
> The problem is that we can easily create a cyclic watermark (time) dependency
> in the stream graph which will result in a deadlock for watermark triggered
> operators such as the `WindowOperator`.
> A solution to this could be to emit a Long.MAX_VALUE watermark from the
> iteration sources.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
