[
https://issues.apache.org/jira/browse/QUARKS-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250504#comment-15250504
]
ASF GitHub Bot commented on QUARKS-131:
---------------------------------------
Github user vdogaru commented on a diff in the pull request:
https://github.com/apache/incubator-quarks/pull/86#discussion_r60467472
--- Diff: api/graph/src/main/java/quarks/graph/Connector.java ---
@@ -115,5 +115,27 @@ Licensed to the Apache Software Foundation (ASF) under
one
*
* @return set of tag values.
*/
- Set<String> getTags();
+ Set<String> getTags();
+
+ /**
+ * Set the alias for the connector.
+ * <p>
+ * The alias must be unique within the topology.
+ * The alias may be used in various contexts:
+ * <ul>
+ * <li>Runtime control services for the connector are registered with
this alias.</li>
--- End diff --
I'm a bit confused by "Runtime control services for the connector". At the
high level, a control service provides an interface for controlling the stream
and is registered with the TStream's alias.
> need easy way to get PeriodicMXBean associated with a poll() invocation
> -----------------------------------------------------------------------
>
> Key: QUARKS-131
> URL: https://issues.apache.org/jira/browse/QUARKS-131
> Project: Quarks
> Issue Type: Improvement
> Reporter: Dale LaBossiere
> Assignee: Dale LaBossiere
>
> I think we're missing some API is missing to make this all usable.
> A Topology/TStream domain user needs an easy way to get the PeriodicMXBean
> for a particular Topology.poll() invocation.
> The PeriodicSource oplet implements PeriodicMXBean which allows changing the
> period.
> The only demonstrated use is by
> DirectJobTest.jobPeriodicSourceCancellation(), which iterates over the
> Topology's underlying graph for instanceof PeriodicSource oplet (it's the
> only ProcessSource oplet in the graph for this test).
> That's certainly not easy / convenient / nor in the "TStream" domain the user
> is mostly operating in.
> [~djd] [~vdogaru] what schemes for addressing this have already been
> considered / decided? Some sort of "control bean registry service" where a
> user gets to supply a name (e.g., to poll()) and the runtime registers the
> bean (e.g., PeriodicMXBean) under that name? If there's not a concrete plan
> lets work on that here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
