[
https://issues.apache.org/jira/browse/FLINK-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643743#comment-15643743
]
Tzu-Li (Gordon) Tai commented on FLINK-5018:
--------------------------------------------
Good idea. This would be relevant only for ingestion time, though. For event
time we can still only rely on a "idle interval", if we don't to go for a
strict "idle timeout".
> User configurable source idle timeout to work with WatermarkStatus emitting
> ---------------------------------------------------------------------------
>
> Key: FLINK-5018
> URL: https://issues.apache.org/jira/browse/FLINK-5018
> Project: Flink
> Issue Type: Sub-task
> Components: Streaming
> Reporter: Tzu-Li (Gordon) Tai
> Fix For: 1.2.0
>
>
> There are 2 cases where sources are considered idle and should emit an idle
> {{WatermarkStatus}} downstream, taking Kafka consumer as example:
> - The source instance was not assigned any partitions
> - The source instance was assigned partitions, but they currently don't have
> any data.
> For the second case, we can only consider it idle after a timeout threshold.
> It would be good to make this timeout user configurable besides a default
> value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
