You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/10/25 14:00:00 UTC

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

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

Stephan Ewen commented on FLINK-5018:
-------------------------------------

I think we can close this issue. This should be subsumed by the new source interface and the new watermark generators.

[~aljoscha] [~tzulitai]

> 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: API / DataStream
>            Reporter: Tzu-Li (Gordon) Tai
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)