[
https://issues.apache.org/jira/browse/EDGENT-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530108#comment-15530108
]
Dale LaBossiere commented on EDGENT-178:
----------------------------------------
One (lame ascii art) example along the lines of the following -- which has
dispensed with the Source/Target stream-id columns as that info is also present
in today's tags columns
===================================================
Name | Oplet Kind | Tuple Count
1 .... 43
Source Streams Target Streams
2: alias: anAlias tags: t1, t2, t3 7: alias: anAlias tags: t1, t2, t3
5: alias: anAlias tags: t1, t2, t3
===================================================
Heads up: some day the Tuple Count field will need attention -- hence
more/wider oplet Tuple Count popup info.
A single value is fine when the #-IN == #-OUT but separate IN/OUT counts will
be needed to handle the more general cases.
And adding tuple cnt values for each Stream above to save users from having to
hover on the aggregate set of streams to see each one's info may also be
appreciated:
5: tuples: 4234098234 alias: anAlias tags: t1, t2, t3
10: tuples: 4234098234 // for the typical case of no alias or tags
> console: stream hover should report "alias" in addition to tags; maybe oplet
> hover too
> --------------------------------------------------------------------------------------
>
> Key: EDGENT-178
> URL: https://issues.apache.org/jira/browse/EDGENT-178
> Project: Edgent
> Issue Type: Improvement
> Components: Console
> Reporter: Dale LaBossiere
> Assignee: Queenie Ma
> Priority: Minor
> Labels: newbie
> Attachments: alias_stream_hover.png
>
>
> TStream.alias("someAlias") manifests itself in graph.Connector similar to
> tags. I'm pretty sure the graph json captures the alias already.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
