edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-147) adaptable TWindow width
Date Mon, 25 Apr 2016 17:59:12 GMT

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

Dale LaBossiere commented on QUARKS-147:

FYI, in https://github.com/apache/incubator-quarks/pull/86  for QUARKS-131 (pending review)
I followed through with the change to rename ``PeriodicMXBean`` to ``PeriodMXBean`` and also
added ``TStream.TYPE="stream"`` and changed ``PeriodicSource`` to register the control with

> adaptable TWindow width
> -----------------------
>                 Key: QUARKS-147
>                 URL: https://issues.apache.org/jira/browse/QUARKS-147
>             Project: Quarks
>          Issue Type: Improvement
>          Components: Runtime
>            Reporter: Dale LaBossiere
> Just like there's a need for adaptable Topology.poll() behavior (QUARKS-131), applications
will need the ability to adapt a window's width as demanded by conditions.
> e.g., maybe a condition occurs that motivates increasing the window width to improve
the accuracy of an analytic.  Or maybe the app decides that it should reduce the width as
a result of processing time or memory pressure concerns.
> Notes:
> - add TWindow.alias(), getAlias()
> - time based window would register and handle PeriodicMXBean
> - count based window would register and handle a new MBean - e.g., CountMXBean ?

This message was sent by Atlassian JIRA

View raw message