[jira] [Commented] (QUARKS-50) stream tags need to be "duplicated" through metric and fanout oplets

["Victor Dogaru (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QUARKS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231183#comment-15231183 ] 

Victor Dogaru commented on QUARKS-50:
-------------------------------------

I am trying to understand how this would work.  I think that for certain oplets, such as Peek (base for metrics oplets) and FanOut, output streams carry the same tuples as their input, so it seems reasonable for input stream tags to propagate to the outputs.

Split and Filter generate output streams which are subsets of their input.  Does it make sense to propagate input stream tags for these oplets?  Similar question for oplets that control the flow of tuples such as Isolate, PressureReliever, etc.

The user may want to deploy tags to indicate adjacent stream equality, but should this be the default behavior?  One may explicitly get tags associated with an input TStream and add them downstream, for example:
{code}
TStream<Double> gaussian = t.poll(() -> r.nextGaussian(), ...);
gaussian.tag("random");

// Carry tags over the peek
TStream<Double> next = gaussian.peek(g -> System.out.println(g));
next.tag(gaussian.getTags().toArray(new String[0]));
{code}


> stream tags need to be "duplicated" through metric and fanout oplets
> --------------------------------------------------------------------
>
>                 Key: QUARKS-50
>                 URL: https://issues.apache.org/jira/browse/QUARKS-50
>             Project: Quarks
>          Issue Type: Improvement
>          Components: Console, Runtime
>            Reporter: Dale LaBossiere
>              Labels: newbie
>         Attachments: Screen Shot 2016-03-21 at 12.46.01 PM.png
>
>
> In a vintage 21Mar console's "static flow" view, stream (tag) coloring isn't retained through metric/peek and fanout oplets.  That makes it more difficult to identify streams.  That's particularly true in conjunction with the desire to minimizing the visual impact of injected metric oplets.  See the streams associated with oplets 12,16,15,21 in the attached image.
> The output streams of those oplets are by definition the same content as the input stream so the input tags should be duplicated on the oplets' output streams.  Seems like a runtime issue not a console issue.



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