[jira] [Updated] (APEXCORE-585) Latency should be calculated only after the first window has been complete

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

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

Vlad Rozov updated APEXCORE-585:
--------------------------------
    Priority: Minor  (was: Major)

> Latency should be calculated only after the first window has been complete
> --------------------------------------------------------------------------
>
>                 Key: APEXCORE-585
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-585
>             Project: Apache Apex Core
>          Issue Type: Bug
>            Reporter: David Yan
>            Assignee: David Yan
>            Priority: Minor
>             Fix For: 3.6.0
>
>
> From the latency unit test, it tries to calculate the latency by looking at the difference between current window id and upstream's current window id when the end window stats is not available. But when the current window id is 0 (first window has not been complete), it would return some wacky latency value because the current window id is 0.
> This would not be an issue if the window id was not a simple sequence.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)