[
https://issues.jboss.org/browse/DROOLS-244?page=com.atlassian.jira.plugin...
]
Vytautas Gimbutas commented on DROOLS-244:
------------------------------------------
What about sliding length window? lets say the code is same, conditions are defined as:
$transactionCreatedEventCount : Number() from accumulate($tce : TransactionCreatedEvent()
over window:length(1) from entry-point "TransactionCreatedEventStream" ,
count($tce))
$transactionCompletedEventCount : Number() from accumulate($tce2 :
TransactionCompletedEvent() over window:length(1) from entry-point
"TransactionCompletedEventStream" , count($tce2))
and @expires metatag is changed to 2 days for both event declarations.
I would expect that after running the test case $transactionCompletedEventCount would be
equal 0, because the event should have expired long ago (in the code timestamp is set to
-30days).
Perhaps the commit fixes also this issue? I don't see SlidingLengthWindow.java edited,
that's why i'm saying this.
Sliding windows working incorrectly when timestamp attribute is
defined
-----------------------------------------------------------------------
Key: DROOLS-244
URL:
https://issues.jboss.org/browse/DROOLS-244
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Vytautas Gimbutas
Assignee: Mark Proctor
Attachments: app-ss-test-case.zip, Event.java, file.drl, Transaction.java,
TransactionCompletedEvent.java, TransactionCreatedEvent.java, TransactionEvent.java
Download app-ss-test-case.zip and run TimestampAttributeTest.
When timestamp attribute is set in the past (lets say with timestamp of 30 days ago) it
falls in every sliding window over time (e.g. 1s).
Expected output:
1
0
Actual output:
1
1
--
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