6:44 p.m.
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and a fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events (it
should fire after the 3rd such event).
in practice the rule never fires. worse, it also retains all the events in memory ehrn it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:44 p.m.
New subject: [JBoss JIRA] Commented: (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
Radai Rosenblatt commented on JBRULES-3075:
-------------------------------------------
im not sure how this relates to https://issues.jboss.org/browse/JBRULES-2881 , since 2881
is marked as fixed in the same version my test is failing for.
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and a fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event).
in practice the rule never fires. worse, it also retains all the events in memory ehrn it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:45 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
Radai Rosenblatt updated JBRULES-3075:
--------------------------------------
Attachment: drools length window bug.zip
maven project demonstrating a bug with fusion window:length in 5.2.0.CR1
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and a fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event).
in practice the rule never fires. worse, it also retains all the events in memory ehrn it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:08 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
Radai Rosenblatt updated JBRULES-3075:
--------------------------------------
Description:
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events (it
should fire after the 3rd such event - when the window contains 3 non-matching events and
the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory ehrn it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
was:
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and a fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events (it
should fire after the 3rd such event).
in practice the rule never fires. worse, it also retains all the events in memory ehrn it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory ehrn it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:28 p.m.
New subject: [JBoss JIRA] Commented: (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
Amit Lieberman commented on JBRULES-3075:
-----------------------------------------
We've seen this behavior too, this is very frustrating.
This actually means the whole "window:length" feature can't be used at all.
events are not cleared from memory and therefor accumulate functions constantly return
wrong results.
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory ehrn it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:29 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
Radai Rosenblatt updated JBRULES-3075:
--------------------------------------
Description:
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events (it
should fire after the 3rd such event - when the window contains 3 non-matching events and
the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
was:
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events (it
should fire after the 3rd such event - when the window contains 3 non-matching events and
the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory ehrn it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 p.m.
New subject: [JBoss JIRA] (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration updated JBRULES-3075:
---------------------------------------------
Bugzilla Update: Perform
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 p.m.
New subject: [JBoss JIRA] (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration updated JBRULES-3075:
---------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=787118
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 p.m.
New subject: [JBoss JIRA] (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3075:
--------------------------------------------------
Tomas Schlosser <tschloss(a)redhat.com> made a comment on [bug
787118|https://bugzilla.redhat.com/show_bug.cgi?id=787118]
Pull request #92 was submitted
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:15 p.m.
New subject: [JBoss JIRA] (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3075:
--------------------------------------------------
Edson Tirelli <etirelli(a)redhat.com> changed the Status of [bug
787118|https://bugzilla.redhat.com/show_bug.cgi?id=787118] from NEW to ASSIGNED
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:55 a.m.
New subject: [JBoss JIRA] (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3075:
--------------------------------------------------
Edson Tirelli <etirelli(a)redhat.com> changed the Status of [bug
787118|https://bugzilla.redhat.com/show_bug.cgi?id=787118] from ASSIGNED to MODIFIED
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:55 a.m.
New subject: [JBoss JIRA] (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
RH Bugzilla Integration commented on JBRULES-3075:
--------------------------------------------------
Edson Tirelli <etirelli(a)redhat.com> made a comment on [bug
787118|https://bugzilla.redhat.com/show_bug.cgi?id=787118]
Tomas, there are some misunderstandings with this test case:
* Up to Drools 5.3, all windows are declared inline in the rules, as in your example, BUT
the order in which the operations are applied is the following:
1. first all filters are applied (e.g., company == 'RHT')
2. then the window is created out of the events that match the filters
3. then the beta constraints are applied (i.e. joins)
The example of using "not" with an inline window is semantically incorrect:
not( StockTick( company == 'RHT' ) over window:length(3) )
Since the filter (company == 'RHT') is applied first, all the events that will
compose the window of length 3 will always be RHT events, and so, the window declaration
is redundant in this case. The above is exactly the same as writing:
not( StockTick( company == 'RHT' ) )
To correctly define a rule that states "if there is no RHT stock ticks in the last 3
StockTicks", up to Drools 5.3, one needs to use 2 patterns:
when
not( $st : StockTick() over window:length(3) and
StockTick( this == $st, company == "RHT" )
)
then
We understand that this is verbose and confusing, as well as heavier at runtime than it
would be necessary. This is one of the reasons that we added named windows to Drools 5.4.
From Drools 5.4+, named windows can be declared outside rules. So, for
instance, the above window could be defined like:
declare window ticks
StockTick() over window:length(3)
end
And then it becomes clear what belongs to the window and what does not. Rules then can
reference that window appropriately:
when
not( StockTick( company == "RHT" ) from window ticks )
then
Behind the scenes, a new algorithm also makes the execution of such windows much more
performant, as well as improves the sharing of window definitions among multiple rules.
* The second misunderstanding is that the expiration of events only happens based on
temporal constraints in Drools. Since the test does not define any temporal constraints or
expiration policies (a window:length is not a temporal constraint), the events are
retained in memory until explicitly retracted. Support to new types of expiration policies
are in our roadmap and will be available in newer versions (e.g., retain only the last 3
events, retain unique events, etc).
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Mark Proctor
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 a.m.
New subject: [JBoss JIRA] (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
Edson Tirelli reassigned JBRULES-3075:
--------------------------------------
Assignee: Edson Tirelli (was: Mark Proctor)
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Edson Tirelli
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:59 a.m.
New subject: [JBoss JIRA] (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
Edson Tirelli resolved JBRULES-3075.
------------------------------------
Fix Version/s: 5.2.1.Final
Resolution: Deferred
I am closing this ticket as Drools 5.3 does not support non-temporal-based expiration
policies. Also, there was a misunderstanding on the semantics of sliding window definition
and usage as explained in my previous comment.
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Edson Tirelli
Fix For: 5.2.1.Final
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:59 a.m.
New subject: [JBoss JIRA] (JBRULES-3075) window:length windows retaining events when they shouldnt
[
https://issues.jboss.org/browse/JBRULES-3075?page=com.atlassian.jira.plug...
]
Edson Tirelli closed JBRULES-3075.
----------------------------------
window:length windows retaining events when they shouldnt
---------------------------------------------------------
Key: JBRULES-3075
URL: https://issues.jboss.org/browse/JBRULES-3075
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.2.0.CR1
Environment: win64, jdk 6u24
Reporter: Radai Rosenblatt
Assignee: Edson Tirelli
Fix For: 5.2.1.Final
Attachments: drools length window bug.zip
using the following DRL:
package contrived.example
import contrived.example.EventWithTimestamp
declare EventWithTimestamp
@role(event)
@duration( duration )
@timestamp( timestamp )
end
rule "no event in window"
when
not EventWithTimestamp (someProp=="whatever") over window:length(3) from
entry-point "Event Stream"
then
System.err.println("retract");
end
if we start with an initial matching (someProp=="whatever") event and fire a
long sequence of non-matching events:
{"something else", "something else" ... "something else"}
the rule should fire sometime into the long chain of "something else" events
(it should fire after the 3rd such event - when the window contains 3 non-matching events
and the 1st matching event has been pushed out).
in practice the rule never fires. worse, it also retains all the events in memory when it
should only keep the last 3.
to reproduce the issue, simply build the attached maven project (mvn clean install)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4627
days inactive
4870
days old
14 comments
4 participants
participants (4)
-
Amit Lieberman (JIRA) -
Edson Tirelli (JIRA)
-
Radai Rosenblatt (JIRA)
-
RH Bugzilla Integration (JIRA)