[
https://issues.apache.org/jira/browse/QUARKS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240497#comment-15240497
]
Dale LaBossiere commented on QUARKS-124:
----------------------------------------
I think that can be accomplished by inserting an "elapsed time filter" right
before the "publish", where the filter function:
- maintains a last-passed-time and min-elapsed-time state
- min-elapsed-time==0 means "pass all"; min-elapsed-time can be changed
dynamically
- in the "pass all" mode: it updates the last-passed-time and passes the tuple
(returns true)
- in the "elapsed time" mode: when it receives a tuple it sees if the
min-elapsed-time has elapsed (e.g., 30min) since last-passed-time. If it has
then it updates last-passed-time and passes the tuple (returns true), otherwise
it filters the tuple out (returns false)
[~djd] does that sort of logic achieve the desired effect / was the scenario
description accurate? If so I'll do a recipe for it. Then I'll see about
creating an "elapsed time filter" to add to quarks.analytics.sensors
> Add a recipe for changing the rate at which data is published
> -------------------------------------------------------------
>
> Key: QUARKS-124
> URL: https://issues.apache.org/jira/browse/QUARKS-124
> Project: Quarks
> Issue Type: Task
> Components: Documentation
> Reporter: Dale LaBossiere
> Assignee: Dale LaBossiere
>
> e.g., analytics are being continuously performed and new results generated
> say every 1min but under "normal" conditions a "normal" result is only
> published (equivalently an IotDevice event generated) every 30min. Some
> alert condition is detected by local analytics and the application wants to
> start publishing the results every 1min.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
