[JBoss JIRA] Created: (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
3:52 p.m.
Rule delayed although temporal operator within not() refers to past events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://jira.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Fix For: 5.2.0.M1
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:01 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Mark Proctor updated JBRULES-2773:
----------------------------------
Fix Version/s: 5.2.0.CR1
(was: 5.2.0.M1)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Fix For: 5.2.0.CR1
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 p.m.
New subject: [JBoss JIRA] Assigned: (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Mark Proctor reassigned JBRULES-2773:
-------------------------------------
Assignee: Edson Tirelli (was: Mark Proctor)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.2.0.CR1
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:36 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2773:
--------------------------------------
Fix Version/s: 5.2.0.CR2
(was: 5.2.0.CR1)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.2.0.CR2
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2773:
--------------------------------------
Fix Version/s: 5.3.0.Beta1
(was: 5.2.0.Final)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.3.0.Beta1
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:41 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2773:
--------------------------------------
Fix Version/s: 5.3.0.CR1
(was: 5.3.0.Beta1)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.3.0.CR1
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2773:
--------------------------------------
Fix Version/s: 5.3.0.Final
(was: 5.3.0.CR1)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.3.0.Final
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:02 p.m.
New subject: [JBoss JIRA] (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2773:
--------------------------------------
Fix Version/s: 5.4.0.Beta1
(was: 5.3.0.Final)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta1
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
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
11:15 a.m.
New subject: [JBoss JIRA] (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2773:
--------------------------------------
Fix Version/s: 5.4.0.Beta2
(was: 5.4.0.Beta1)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta2
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
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
11:26 a.m.
New subject: [JBoss JIRA] (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Geoffrey De Smet updated JBRULES-2773:
--------------------------------------
Fix Version/s: 5.4.0.Beta3
(was: 5.4.0.Beta2)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.4.0.Beta3
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
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
9:37 a.m.
New subject: [JBoss JIRA] (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Toni Rikkola updated JBRULES-2773:
----------------------------------
Fix Version/s: 5.4.0.Final
(was: 5.4.0.CR1)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.4.0.Final
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
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
2:01 p.m.
New subject: [JBoss JIRA] (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Toni Rikkola updated JBRULES-2773:
----------------------------------
Fix Version/s: 5.5.0.Beta1
(was: 5.4.0.Final)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.5.0.Beta1
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
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
11:28 a.m.
New subject: [JBoss JIRA] (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Michael Anstis updated JBRULES-2773:
------------------------------------
Fix Version/s: 5.5.0.CR1
(was: 5.5.0.Beta1)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 5.5.0.CR1
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 p.m.
New subject: [JBoss JIRA] (JBRULES-2773) Rule delayed although temporal operator within not() refers to past events
[
https://issues.jboss.org/browse/JBRULES-2773?page=com.atlassian.jira.plug...
]
Michael Anstis updated JBRULES-2773:
------------------------------------
Fix Version/s: 6.0.0.Beta1
(was: 5.5.0.CR1)
Rule delayed although temporal operator within not() refers to past
events
--------------------------------------------------------------------------
Key: JBRULES-2773
URL: https://issues.jboss.org/browse/JBRULES-2773
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Edson Tirelli
Fix For: 6.0.0.Beta1
The .drl:
declare Leave
@role( event )
@timestamp( timestamp )
end
rule "XXX Leave not !="
when
$leave: Leave()
not Leave( this != $leave )
then
System.out.println( "XXX only one Leave - not !=" );
end
rule "YYY Leave not after"
when
$leave: Leave()
not Leave( this before $leave )
then
System.out.println( "YYY only one Leave - not before" );
end
A) The pseudo-clock is advanced according to the timestamp; then
exactly one event Leave is inserted; then fireAllRules() is called.
1) Running in CLOUD mode, both rules fire.
2) But running in STREAM mode, ONLY rule XXX fires.
B) Like A, but the session clock is advanced by (at least) 1ms
prior to calling fireAllRules().
3) Either mode, both rules fire.
I think that A2) is incorrect; why should passing another msec change the logic? Rule YYY
matches by looking into the past, so the "rule activation delay" described in
2.5.2.2. Negative Patterns in Stream Mode should not apply because the default parameter
for before is [1ms,...].
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4211
days inactive
4929
days old
13 comments
6 participants
participants (6)
-
Geoffrey De Smet (JIRA) -
Geoffrey De Smet (Updated) (JIRA)
-
Mark Proctor (JIRA)
-
Michael Anstis (JIRA)
-
Toni Rikkola (JIRA)
-
Wolfgang Laun (JIRA)