[EDGENT-137] Tuple count: Source oplet flows into Peek. Source tuple count is less than Peek’s count

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Component/s: Console
• Assignee: Susan L. Cline
• Reporter: May Wone
• Created: 08/Apr/16 19:08
• Updated: 02/Jan/18 19:31
• Resolved: 27/May/16 14:03

Description

Oplet 0 is a SupplierPeriodicSource with tuple count 98 and target oplet 1.
Oplet 1 is a Peek with tuple count 415.
Since peek does not change the tuples, it looks odd the source’s tuple count is less than the peek’s tuple count.
Note that Peek's target is an implicit fanout oplet.

Testcase quarks.test.svt.apps.FleetManagementAnalyticsClientApplication