[
https://issues.apache.org/jira/browse/FLINK-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tzu-Li (Gordon) Tai updated FLINK-5018:
---------------------------------------
Description:
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.
was:
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.
> 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: Streaming
> Reporter: Tzu-Li (Gordon) Tai
>
> 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
(v6.3.15#6346)
