[jira] [Commented] (FLINK-5018) Make source idle timeout user configurable

["vinoyang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732743#comment-16732743 ] 

vinoyang commented on FLINK-5018:
---------------------------------

I am going to start implementing this issue. Currently {{idleTimeout}} is set to -1 and injected via {{StreamSourceContexts#getSourceContext}} as a parameter (this method is responsible for instantiating the {{ManualWatermarkContext}} and {{AutomaticWatermarkContext}}). My initial idea is to add a configuration method for {{ExecutionConfig}}, such as "setIdleTimeout". What do you think? [~tzulitai] [~eronwright]

> Make source idle timeout user configurable
> ------------------------------------------
>
>                 Key: FLINK-5018
>                 URL: https://issues.apache.org/jira/browse/FLINK-5018
>             Project: Flink
>          Issue Type: Sub-task
>          Components: DataStream API
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: vinoyang
>            Priority: Major
>
> There are 2 cases where sources are considered idle and should emit an idle {{StreamStatus}} 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
(v7.6.3#76005)