edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-131) need easy way to get PeriodicMXBean associated with a poll() invocation
Date Wed, 27 Apr 2016 16:28:12 GMT

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

ASF GitHub Bot commented on QUARKS-131:
---------------------------------------

Github user dlaboss commented on a diff in the pull request:

    https://github.com/apache/incubator-quarks/pull/86#discussion_r61290360
  
    --- Diff: api/oplet/src/main/java/quarks/oplet/OpletContext.java ---
    @@ -76,6 +76,12 @@ Licensed to the Apache Software Foundation (ASF) under one
         List<? extends Consumer<O>> getOutputs();
     
         /**
    +     * Get the oplet's output port context information.
    +     * @return list of {@link OutputContext}, one for each output port.
    +     */
    +    List<? extends OutputContext> getOutputContext();
    --- End diff --
    
    fixed


> 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)

Mime
View raw message