[jira] [Closed] (FLINK-7728) StatusWatermarkValve has different min watermark advancement behavior depending on the ordering inputs become idle

2018-03-12 Thread Tzu-Li (Gordon) Tai (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tzu-Li (Gordon) Tai closed FLINK-7728.
--
   Resolution: Fixed
Fix Version/s: (was: 1.3.3)
   1.3.4

> StatusWatermarkValve has different min watermark advancement behavior 
> depending on the ordering inputs become idle
> --
>
> Key: FLINK-7728
> URL: https://issues.apache.org/jira/browse/FLINK-7728
> Project: Flink
>  Issue Type: Bug
>  Components: DataStream API
>Affects Versions: 1.2.1, 1.4.0, 1.3.2
>Reporter: Tzu-Li (Gordon) Tai
>Assignee: Tzu-Li (Gordon) Tai
>Priority: Blocker
> Fix For: 1.3.4, 1.4.0
>
>
> Currently, once all inputs of a {{StatusWatermarkValve}} becomes idle, we 
> only emit the {{StreamStatus.IDLE}} marker, and check nothing else. This 
> makes the watermark advancement behavior inconsistent in the case that all 
> inputs become idle, depending on the order that they become idle.
> Consider the following setup:
> {code}
> Channel #1: Watermark 10, ACTIVE
> Channel #2: Watermark 5, ACTIVE
> Channel #3: Watermark 5, ACTIVE
> {code}
> If the channels become IDLE with the order #2 -> #3 -> #1, watermark 10 will 
> be emitted as the new min watermark once both #2 and #3 becomes idle.
> On the other hand, if the order is #1 -> #2 -> #3, watermark 10 will not be 
> emitted.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (FLINK-7728) StatusWatermarkValve has different min watermark advancement behavior depending on the ordering inputs become idle

2017-10-02 Thread Aljoscha Krettek (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aljoscha Krettek closed FLINK-7728.
---
   Resolution: Fixed
Fix Version/s: (was: 1.2.2)

Fixed on release-1.3 in
4dcd9fba21eef157063d2d70b0e55869009f2954
2875260d067c1e6754a248b8e281516ad9b5a269
c528139c3c2b33ba7bd11df154ba204408713b02

> StatusWatermarkValve has different min watermark advancement behavior 
> depending on the ordering inputs become idle
> --
>
> Key: FLINK-7728
> URL: https://issues.apache.org/jira/browse/FLINK-7728
> Project: Flink
>  Issue Type: Bug
>  Components: DataStream API
>Affects Versions: 1.2.1, 1.4.0, 1.3.2
>Reporter: Tzu-Li (Gordon) Tai
>Assignee: Tzu-Li (Gordon) Tai
>Priority: Blocker
> Fix For: 1.4.0, 1.3.3
>
>
> Currently, once all inputs of a {{StatusWatermarkValve}} becomes idle, we 
> only emit the {{StreamStatus.IDLE}} marker, and check nothing else. This 
> makes the watermark advancement behavior inconsistent in the case that all 
> inputs become idle, depending on the order that they become idle.
> Consider the following setup:
> {code}
> Channel #1: Watermark 10, ACTIVE
> Channel #2: Watermark 5, ACTIVE
> Channel #3: Watermark 5, ACTIVE
> {code}
> If the channels become IDLE with the order #2 -> #3 -> #1, watermark 10 will 
> be emitted as the new min watermark once both #2 and #3 becomes idle.
> On the other hand, if the order is #1 -> #2 -> #3, watermark 10 will not be 
> emitted.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)