Hi Edson,
Many thanks for taking the time to respond. I think I should be able to
develop something using
the controlled clock approach outlined below.
Thanks again, and keep up the great work!
Best Regards,
Paul
2010/3/30 Edson Tirelli
>
>Hi Paul,
>
>Unfortunately, the bottom lin
Hi Paul,
Unfortunately, the bottom line is that there is no magic. Time windows
are always based on the concept of "current time" and to be able to join
different streams of events Drools took the decision of having a
session-scoped clock.
The major problem of a fact timestamp be in the
Hi Edson.
Many thanks for the response. Firing the rules before advancing the clock
fixes the problem. However,
I'm now looking for suggestions on how I can use time windows - when I have
events arriving from multiple
unsynchronized streams :)
For example, I have two events StreamOne and StreamTw
Did you tried firing the rules before advancing the time clock?
This is a very tricky situation because you are working with the edge
limits of the time window. Events are expired from the time window when the
clock advances. You are inserting events every 5 seconds. So, lets say you
insert
Meant to say: using drools 5.0.1.
- Paul
On Fri, Mar 26, 2010 at 1:22 AM, Paul R. wrote:
> Hi,
>
> I'm using an accumulate on a sliding window to count the number of events,
> which occur in a 30 second window;
> the events are inserted every 5 seconds - so with a 30 second window, I
> would ex
Hi,
I'm using an accumulate on a sliding window to count the number of events,
which occur in a 30 second window;
the events are inserted every 5 seconds - so with a 30 second window, I
would expect 6 events to occur.
The rule below never fires, though from the log output, it looks as though
the
