Hi there,
I can't seem to find a hint in the documentary about WHEN an event is
considered to be recognized by a sliding time window.
I tried it out myself with an event with a duration of 5000 (= 5s) and a
rule with a sliding time window of just 1s. So the event can never be
completely
Its impossible to add an out-identifier (which is pretty bad). The JSON
Marshaller works fine, though.
Can I get a clean implementation somewhere?
Exception:
Exception in thread main java.lang.NullPointerException
at
Yeah..the topic subject explains itself, I presume :)
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/How-to-obtain-the-timestamp-of-an-event-if-I-don-t-use-an-timestamp-attribute-tp2443366p2443366.html
Sent from the Drools - User mailing list archive at
Yes, you're right, Wolfgang. As I only use fast-and-easy-to-understand rules
on the forum, I truncated some of the actual rule because I thought this
wouldn't have an effect. Strangely, it does.
In my rule, there is, like in yours, another easy pattern before the collect
statement.
--
View this
No I don't modify any LoopDetectorEvent.Actually, in some situations the rule
fires even more than two times for some Sensors.
I don't use the logger. I just do System.out.println's to see when a rule
fires. . If you need any more info, then I will use the logger for you. What
information might
Hi folks, another bug discovered here?
This rule yields a really nice exception
rule Test
when
$list : List() from collect ( A() over window:time(5s) )
Number($avg : doubleValue) from accumulate( A($num : num)
from $list, average($num))
then
Thank you.
I found the main problem, though.
In the camel-client.xml, the route points to
cxfrs://http://localhost:8080/drools-server-app/kservice/rest
but cxfrs://http://localhost:8080/drools-5.1.1-server/kservice/rest is
right. Then it works, if I also apply your little hint. Thanks.
Now
Hello folks.
Got a new characteristic unveiled,...
if I have a rule like this (with Fusion in STREAM mode)...
(Sensor is a fact)
rule Test
timer(int: 7s 7s)
when
$sensor : Sensor()
Number($avg : doubleValue 0.0) from accumulate
Hi there.
I was trying to setup the Drools Server. As I understand, this is not a
server per se, its just the usual Drools with some framework plumbing. But I
appreciate not having to do that myself. But I can't get it to work.
I imported the .war file into my Eclipse and tried to deploy it to
HI Esteban,
thanks for your hint.. But it didn't work out.. startup was fine again, now
only without that INFO. But still impossible to run the test.jsp. There's
still this single warning (WARNUNG) in the log. Does that happen to be a
problem?
Anyone got ideas?
--
View this message in context:
@Greg: Could you hand me a link to that discussion?
@Wolfgang: I guess you are referring to the list I use. Of course I expect
them to be ordered by timestamp.
--
View this message in context:
Hey again everyone,
I seem to be having another problem.
When I have a rule like that
when
A() over window:length(1)
B() over window:length(1)
then
...
I imagine now having two windows of length 1. One always keeping the latest
A event and one always keeping
Hello everyone.
Lets say we have StockTicks...
Is it possible to detect a monotonically decreasing StockTick stream over a
window?
If I knew the number of events I want to check on, I'd do it this way
$a : StockTick() over window:time(20s)
$b : StockTick(this after $a, price $a.price)
Hello everyone.
Lets say we have StockTicks...
Is it possible to detect a monotonically decreasing StockTick stream over a
window?
If I knew the number of events I want to check on, I'd do it this way
$a : StockTick() over window:time(20s)
$b : StockTick(this after $a, price $a.price) over
Hey again everyone,
I seem to be having another problem.
When I have a rule like that
when
A() over window:length(1)
B() over window:length(1)
then
...
I imagine now having two windows of length 1. One always keeping the latest
A event and one always keeping the
Hello there and a happy new year to everyone reading :)
Why am I here again? Yep, got a problem. Don't know why it doesn't work. I'm
using the latest snapshot version.
So here it goes.
A simple rule with conjunction and disjunction but over a set of events.
when
$ldes
Hello there.
I seem to have trouble with the timer operator which is documented to have
superseded the duration operator for use in the rule body. I might have
something to do with the not operator I use in my rule.
Scenario: A is a fact, B is an event
When I write something like this
rule
I ran a few more tests and it seems that duration is also not capable of
achieving the expected results.
If you have a lot of different A objects in the example, and a few more
complex conditions in the LHS, the rule will only fire for a few A objects,
omitting the rest, when the duration timer
Thanks,
unfortunately not working, either.
Maybe it will help, if I describe the scenario more detailed.
I have three A facts inserted at the beginning.
Then the rule fires the first time after 5 seconds for every A fact and
inserts the B events.
Then I retract ONE of the B events, but the rule
Hi there,
I'm experiencing the same problem using Drools 5.1.1
Whats the status on this?
By the way. It also doesn't work the other way round with
not (exists(X(y != z)))
which is basically the same as
forall($x : X()
X(this == $x, y == z)
)
If this is still a problem,
20 matches
Mail list logo
