Re: plugins/triggers/coprocessors

2011-02-16 Thread Jeremy Hanna
trigger parameter, is the "new" value. >>>> The trigger cannot see the "old" value. >>>>> • Triggers are executed asynchronously some time after the write >>>> which fired it is acknowledged to the client. >>>>> • Trigger

Re: plugins/triggers/coprocessors

2011-02-11 Thread Jeremy Hanna
tation, which is the trigger parameter, is the "new" value. >>> The trigger cannot see the "old" value. >>>> • Triggers are executed asynchronously some time after the write >>> which fired it is acknowledged to the client. >>>>

Re: plugins/triggers/coprocessors

2011-02-11 Thread Jeff Hodges
edged to the client. >> >       • Triggers are executed once during normal execution. We guarantee >> "at least once" execution in case of node failures. >> > Cheers, >> > Maxim >> > >> > >> > On Thu, Feb 10, 2011 at 8:45 AM, Jer

Re: plugins/triggers/coprocessors

2011-02-11 Thread Stu Hood
me after the write > which fired it is acknowledged to the client. > > • Triggers are executed once during normal execution. We guarantee > "at least once" execution in case of node failures. > > Cheers, > > Maxim > > > > > > On T

Re: plugins/triggers/coprocessors

2011-02-11 Thread Jeremy Hanna
d it is acknowledged to the client. > • Triggers are executed once during normal execution. We guarantee "at > least once" execution in case of node failures. > Cheers, > Maxim > > > On Thu, Feb 10, 2011 at 8:45 AM, Jeremy Hanna > wrote: > >