Change @expires policy to override temporal requirements and behaviours ----------------------------------------------------------------------- Key: JBRULES-2578 URL: https://jira.jboss.org/browse/JBRULES-2578 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.1.0.M2, 5.1.0.M1, 5.0.1.FINAL, 5.0.0.FINAL Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.1.0.CR1 Up until now, the @expires policy was handled by the engine as a hint on the expiration offset for events, but that was causing several mistakes and misunderstanding by users. So, change the @expires policy to override and set a definitive expiration offset for events. Example: declare StockTick @role( event ) @expires( 10m ) end The above will cause StockTick events to be expired after 10m in memory, even if rules use temporal operators or sliding windows that would retain the event for more time, or would not require the event to be in memory for that amount of time. -- 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