[
https://issues.apache.org/jira/browse/QUARKS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale LaBossiere resolved QUARKS-137.
------------------------------------
Resolution: Fixed
The missing stream width/flow preceding the peek and the missing stream
width/flow for the fanout outputs is fixed by the "metric propagation" in
QUARKS-22 / PR-116. The peek reports the same tuple count as the source. (not
sure that those changes were responsible for that though).
The FanOut reports, and is scaled for: #fanouts * #incoming. There's always an
issue of whether to report / size an operator based on it's # incoming tuples
or # outgoing tuples or a sum of them.
For FanOut, using #outgoing seems misleading / distracting as the fanout is a
no-op with respect to "real work". It's not analyzing or synthesizing tuples.
Hence at most I think it should use just #incoming. Better yet(?), I could
imagine using some other representation for this oplet to downplay its
significance... perhaps the "rectangle" used by metrics and streamscope oplets.
So I'm closing this jira. If after playing with the updated behavior folks
agree that the FanOut oplet presentation should be changed, another jira can be
created to track that.
> 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
> Components: Console
> Reporter: May Wone
> Assignee: Susan L. Cline
> 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)
