Hello.
Indeed, I have tested with the @expires and the objects are discarded in
this case. What I had understood in the documentation is precisely the
other way that the engine is expected to control the events expiration :
"Inferred Expiration" (8.8.2), when no temporal constraint involves the
objects, they are discarded.
This seems the best way to be sure to eliminate as soon as possible all
the useless objects, whatever their life time. This is particularly
important with flows of thousands of events per second.
Perhaps I don't understand this well... Another idea or advice ?
Thanks for your help.
Regards.
Ephemeris Lappis
Le 27/08/2014 15:30, marianbuenosayres [via Drools] a écrit :
I think that if you want the automatic event lifecycle management to
delete your events, you first need to notify the engine when an event
is old enough to realise it should be removed. This has to be managed
adding the @expires annotation to the event declaration:
declare Notification
@role( event )
@expires ( 1h45m )
end
That will let the engine know it should remove the event from the
working memory (if no rule needs it) after an hour and 45 minutes.
Please check the doc about @expires in the following link:
http://docs.jboss.org/drools/release/6.1.0.Final/drools-docs/html_single/...
Cheers,
------------------------------------------------------------------------
If you reply to this email, your message will be added to the
discussion below:
http://drools.46999.n3.nabble.com/Drools-Fusion-CEP-event-life-cycle-tp40...
To unsubscribe from Drools Fusion (CEP) & event life cycle, click here
<
http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscr...;.
NAML
<
http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=macro_vi...
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Fusion-CEP-event-life-cycle-tp40...
Sent from the Drools: User forum mailing list archive at
Nabble.com.