[erlang-questions] [ANN:] erlang_cep a new Complex Event Processing Library
Dan Macklin
danmacklin10@REDACTED
Tue May 7 08:05:08 CEST 2013
> However, I fail to see the reason why this might be useful in this
> case, as I cannot see any REST API, and reduce functions are quite
> expensive (thus I imply there is no notion of "request", where you can
> implement your match/reduce functions).
Hi,
You're right the reduce is similar to Riak or CouchDB. I wanted to give
users the ability to iterate over matches within a window and perform logic
over them before the results are passed onto a subscribed process (this
could just be output formatting or simple averaging logic). The difference
here is that the reduce function only runs when the CEP system finds a
match, and you can control the size of the matched data. This should mean
that the amount of data that the reduce runs over is quite small.
However a rest interface seems a great idea, why didn't I think of that! So
I'll add it to my todo list.
Many thanks
Dan
On Tuesday, May 7, 2013, Motiejus Jakštys wrote:
> On Tue, May 7, 2013 at 12:54 AM, Richard A. O'Keefe <ok@REDACTED<javascript:;>>
> wrote:
> >
> > On 7/05/2013, at 6:41 AM, Dan Macklin wrote:
> >
> >> I'd like to announce the first beta release of erlang_cep.
> >
> > Looks interesting. I have just begun to read the documentation,
> > but I don't understand why Erlang code should be specifying
> > what to do by stuffing Javascript code into binaries instead of
> > using Erlang functions.
>
> The idea is the same in Riak (like mentioned in the announcement),
> they provide an option to use javascript for map/reduce
> implementation. Same here: implement "reduce" logic in javascript.
>
> However, I fail to see the reason why this might be useful in this
> case, as I cannot see any REST API, and reduce functions are quite
> expensive (thus I imply there is no notion of "request", where you can
> implement your match/reduce functions).
>
> --
> Motiejus Jakštys
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130507/04bfbf72/attachment.htm>
More information about the erlang-questions
mailing list