Return-Path: X-Original-To: apmail-quarks-dev-archive@minotaur.apache.org Delivered-To: apmail-quarks-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4DE5E198C6 for ; Wed, 20 Apr 2016 19:25:29 +0000 (UTC) Received: (qmail 96538 invoked by uid 500); 20 Apr 2016 19:25:29 -0000 Delivered-To: apmail-quarks-dev-archive@quarks.apache.org Received: (qmail 96505 invoked by uid 500); 20 Apr 2016 19:25:29 -0000 Mailing-List: contact dev-help@quarks.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@quarks.incubator.apache.org Delivered-To: mailing list dev@quarks.incubator.apache.org Received: (qmail 96494 invoked by uid 99); 20 Apr 2016 19:25:29 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2016 19:25:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 89551C0338 for ; Wed, 20 Apr 2016 19:25:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.216 X-Spam-Level: X-Spam-Status: No, score=-4.216 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id nGHcY69Qha1n for ; Wed, 20 Apr 2016 19:25:26 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with SMTP id 4FE6F5F256 for ; Wed, 20 Apr 2016 19:25:26 +0000 (UTC) Received: (qmail 95972 invoked by uid 99); 20 Apr 2016 19:25:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Apr 2016 19:25:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8D8302C1F54 for ; Wed, 20 Apr 2016 19:25:25 +0000 (UTC) Date: Wed, 20 Apr 2016 19:25:25 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@quarks.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (QUARKS-124) Add a recipe for changing the rate at which data is published MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/QUARKS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250539#comment-15250539 ] ASF GitHub Bot commented on QUARKS-124: --------------------------------------- GitHub user dlaboss opened a pull request: https://github.com/apache/incubator-quarks/pull/94 [QUARKS-124] add tests for Deadtime You can merge this pull request into a Git repository by running: $ git pull https://github.com/dlaboss/incubator-quarks quarks-124-deadtime-tests Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-quarks/pull/94.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #94 ---- commit 6b10e55255d07b5420b161907bcbc034ca396c3a Author: Dale LaBossiere Date: 2016-04-20T19:23:21Z [QUARKS-124] add tests for Deadtime ---- > 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)