[jira] [Updated] (QUARKS-137) Tuple count: Source oplet flows into Peek. Source tuple count is less than Peek’s count

["May Wone (JIRA)" <ji...@apache.org>]

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

May Wone updated QUARKS-137:
----------------------------
    Attachment: SourceToPeekTupleCount.doc

Attached file with screenshots and instructions for reproducing symptom.

> Tuple count: Source oplet flows into Peek. Source tuple count is less than Peek’s count
> ---------------------------------------------------------------------------------------
>
>                 Key: QUARKS-137
>                 URL: https://issues.apache.org/jira/browse/QUARKS-137
>             Project: Quarks
>          Issue Type: Bug
>            Reporter: May Wone
>            Priority: Minor
>         Attachments: SourceToPeekTupleCount.doc
>
>
> 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



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