[
https://issues.apache.org/jira/browse/APEXCORE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716901#comment-15716901
]
ASF GitHub Bot commented on APEXCORE-585:
-----------------------------------------
GitHub user davidyan74 opened a pull request:
https://github.com/apache/apex-core/pull/427
APEXCORE-585 #resolve do not try to calculate latency if the first wi…
…ndow has not complete
@vrozov please review and merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davidyan74/apex-core APEXCORE-585
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/427.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #427
----
commit 44ceea2af247256c27e1de51423bbdf1d590c04d
Author: David Yan <[email protected]>
Date: 2016-12-02T23:55:04Z
APEXCORE-585 #resolve do not try to calculate latency if the first window
has not complete
----
> 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
>
> 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)
