Hi <span class="gD">Wolfgang,<br>thanks a lot for the explanation, but i am very sad now.<br>I have to use STREAM mode, because i am implementing a spatio-temporal expert system, so, i need of temporal reasoning. I need to compare events on time too.<br>
>From my understaning, i am limitated by:<br></span><ul><li><span class="gD">i cannot update timestamp and duration of an event;</span></li><li><span class="gD">i cannot insert a new event with an old timestamp</span></li>
</ul><p>is it right?</p><p>In a realtime sensor system, i don't receive the event with duration, but i need to correlate them to have an event with duration.</p><p>Do you have any suggestions?</p><p>Thanks a lot,</p><p>
Matteo.<br></p><span class="gD"><br></span><br><div class="gmail_quote">On Thu, Feb 23, 2012 at 7:39 AM, Wolfgang Laun <span dir="ltr"><<a href="mailto:wolfgang.laun@gmail.com">wolfgang.laun@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 22/02/2012, Edson Tirelli <<a href="mailto:ed.tirelli@gmail.com">ed.tirelli@gmail.com</a>> wrote:<br>
> If your use case somehow has "mutable" events, you can retract, change<br>
> the duration and reinsert.<br>
<br>
</div>But mind the requirements of STREAM mode: Events in each stream must<br>
be time-ordered. I.e., inside a given stream, events that happened<br>
first must be inserted first into the engine. If reinsertions would<br>
violate this, you must run the session in CLOUD mode, which has<br>
certain consequences. This is all very well described in the Fusion<br>
manual, section on "Event Processing Modes".<br>
<br>
-W<br>
<div class="im"><br>
<br>
> The engine uses optimizations for the temporal<br>
> reasoning that are based on the fact that events should be immutable. That<br>
> is why the engine "resolves" the timestamp/duration attributes at insert<br>
> time and make them immutable.<br>
><br>
> Edson<br>
><br>
> 2012/2/22 Matteo Cusmai <<a href="mailto:cusmaimatteo@gmail.com">cusmaimatteo@gmail.com</a>><br>
><br>
>> Hi Edson,<br>
>> so, when i want modify an event, i could do as follow:<br>
>><br>
</div>>> - clone event;<br>
>> - change the duration<br>
>> - retract the previuos event<br>
>> - insert the new event<br>
<div class="HOEnZb"><div class="h5">>><br>
>> Is it right?<br>
>><br>
>> Bye bye,<br>
>><br>
>> Matteo.<br>
>><br>
>> 2012/2/22 Edson Tirelli <<a href="mailto:ed.tirelli@gmail.com">ed.tirelli@gmail.com</a>><br>
>><br>
>>><br>
>>> Unfortunately you can't update event durations or timestamp. Events<br>
>>> are supposed to represent things that happened and as so, are immutable<br>
>>> (other than data enrichment). If an event representation is no longer<br>
>>> true,<br>
>>> that event has to be retracted. Most common case is when you are dealing<br>
>>> with atomic events (like start and end atomic events) that represent a<br>
>>> complex event. Usually you will have a rule that correlates the start and<br>
>>> end atomic events and creates a complex derived event, retracting the<br>
>>> atomic ones.<br>
>>><br>
>>> Edson<br>
>>><br>
>>> 2012/2/22 Matteo Cusmai <<a href="mailto:cusmaimatteo@gmail.com">cusmaimatteo@gmail.com</a>><br>
>>><br>
>>>><br>
>>>> Hi all,<br>
>>>> i am using Drools Fusion in multi sensor data fusion system. I have some<br>
>>>> rules that generate a new event when some situations occur. But from the<br>
>>>> other hand, i would like to update the event, when i understand that new<br>
>>>> sensor observation is referring to the same event. I have my Event clazz<br>
>>>> with duration field, i try to update it in modify clause, but i have<br>
>>>> concern about it, because when i use temporal operator (such as before,<br>
>>>> meets, so on) it seems that Drools manage them as event with duration<br>
>>>> null.<br>
>>>> I could post the code too.<br>
>>>> Bye bye,<br>
>>>> Matteo.<br>
>>>> _______________________________________________<br>
>>>> rules-users mailing list<br>
>>>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
>>>><br>
>>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Edson Tirelli<br>
>>> JBoss Drools Core Development<br>
>>> JBoss by Red Hat @ <a href="http://www.jboss.com" target="_blank">www.jboss.com</a><br>
>>><br>
>>> _______________________________________________<br>
>>> rules-users mailing list<br>
>>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
>>><br>
>>><br>
>><br>
>> _______________________________________________<br>
>> rules-users mailing list<br>
>> <a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
>><br>
>><br>
><br>
><br>
> --<br>
> Edson Tirelli<br>
> JBoss Drools Core Development<br>
> JBoss by Red Hat @ <a href="http://www.jboss.com" target="_blank">www.jboss.com</a><br>
><br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</div></div></blockquote></div><br>