[
https://issues.apache.org/jira/browse/QUARKS-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale LaBossiere resolved QUARKS-169.
------------------------------------
Resolution: Fixed
Assignee: Dale LaBossiere
The QUARKS-22 / PR-116 changes fixed this by virtue of its "propagating" edge
counter metric values downstream/upstream across peeks.
> Console: hover on stream between Filter and Peek doesn't report tuple count
> ---------------------------------------------------------------------------
>
> Key: QUARKS-169
> URL: https://issues.apache.org/jira/browse/QUARKS-169
> Project: Quarks
> Issue Type: Bug
> Components: Console
> Reporter: Dale LaBossiere
> Assignee: Dale LaBossiere
> Priority: Minor
> Labels: newbie
> Attachments: Screen Shot 2016-05-04 at 12.48.19 PM.png
>
>
> In the attached image, the oplet 1 is a Filter and oplet 2 is a Peek (from an
> application TStream.peek()). Hover on the Peek correctly reports the number
> of tuples it has received. Hover on the stream connecting the two doesn't
> report the tuple count; it reports "No value - counter not present".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
