[
https://issues.apache.org/jira/browse/QUARKS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248908#comment-15248908
]
ASF GitHub Bot commented on QUARKS-124:
---------------------------------------
Github user ddebrunner commented on a diff in the pull request:
https://github.com/apache/incubator-quarks/pull/91#discussion_r60329452
--- Diff:
analytics/sensors/src/main/java/quarks/analytics/sensors/Filters.java ---
@@ -114,4 +114,27 @@ private Filters() {}
return stream.filter(new Deadband<>(value, inBand));
}
+
+ /**
+ * A filter that discards tuples received during the "deadtime period"
+ * following a tuple this is allowed to pass through.
+ * <p>
+ * E.g., for a deadtime period of 30 minutes, after letting a tuple
+ * pass through, any tuples received during the next 30 minutes are
+ * filtered out. Then the next arriving tuple is passed through and
+ * a new deadtime period is begun.
+ * </p><p>
+ * See {@link Deadtime} for information about changing the deadtime
period
--- End diff --
Is this for the future, as there's no mechanism for the caller of this
method to change the period?
> 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)
