Mailing-List: contact dev-help@streams.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@streams.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jletourneau80@gmail.com
 designates 209.85.223.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <002C46140B2DCC4D8323F87F498E7A0426EF1B70@IMCMBX04.MITRE.ORG>
References: <002C46140B2DCC4D8323F87F498E7A0426EF1B70@IMCMBX04.MITRE.ORG>
Date: Mon, 3 Jun 2013 22:52:01 -0400
Message-ID: 
 <CAL8syOYTJSKOB_f0yUxCTNgYkeNbRUT5fLSE3kLCDn3XawCZ-Q@mail.gmail.com>
Subject: Re: Question about processing architecture
From: Jason Letourneau <jletourneau80@gmail.com>
To: "dev@streams.incubator.apache.org" <dev@streams.incubator.apache.org>
Content-Type: multipart/alternative; boundary=047d7b10cd6f61703204de4b2a5b

--047d7b10cd6f61703204de4b2a5b
Content-Type: text/plain; charset=ISO-8859-1

The current vision is that filters will be implemented agnostic to the
overall processing architecture - there may be subscribers using lucene dsl
as part of the initial streams implemetation- but the interface won't
dictate how a subscriber filters it's activities - I don't know that we've
figured out whether the subscriber delegate tells the aggregate its filter
via an interface or whether aggregator tells each subscriber about every
activity and the subscriber filters - either way - you can implement
filters however you want - provides they adhere to the common filter
interface (which to my recollection is very simplistic)

On Monday, June 3, 2013, Lavender, Beth A wrote:

> Many of our current systems that will feed the integrated activity stream
> are noisy. For example, if I update a page 4 times in  5 minutes it
> generates an activity for each one.   I want to be able to set rule for
> discard the last n activities if they have the same actor, verb, and object
>  in x time frame.
>
> This assumes a sub processor that detects the pattern and takes an action
> described in a rule. Where do rules and sub processors fit in this
> architecture? Is anyone doing this in their existing systems?
>
>

--047d7b10cd6f61703204de4b2a5b--