[
https://issues.apache.org/jira/browse/QUARKS-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270944#comment-15270944
]
ASF GitHub Bot commented on QUARKS-50:
--------------------------------------
GitHub user dlaboss opened a pull request:
https://github.com/apache/incubator-quarks/pull/105
[QUARKS-50] duplicate tags across Peek and FanOut
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dlaboss/incubator-quarks quarks-50-promoteTags
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-quarks/pull/105.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #105
----
commit 9589cc0238df26bb02a648a2e55617c5c95010d9
Author: Dale LaBossiere <[email protected]>
Date: 2016-05-04T16:26:41Z
[QUARKS-50] duplicate tags across Peek and FanOut
----
> 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
> Assignee: 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)
