cool, Thank you !
On Sun, Sep 17, 2017 at 11:58 PM, Grainier Perera wrote:
> Hi Jay,
>
> In that case, you can either remove events from the table which are older
> than 24hrs, or you can include a condition to the join query to ignore
> events that are older than 24hrs. Please refer to the samp
Hi Jay,
In that case, you can either remove events from the table which are older
than 24hrs, or you can include a condition to the join query to ignore
events that are older than 24hrs. Please refer to the sample below;
@Plan:name('TestExecutionPlan')
> define stream publisher (pid string, time
Hi Grainier,
even table approach make sense, but is there a way to limit the event table
to keep the events for let say 24 hour or so and then discard it ?
Thanks for looking into this.
Jay
On Thu, Sep 14, 2017 at 11:51 PM, Grainier Perera wrote:
> Hi Jay,
>
> In your pattern, when a match
Hi Jay,
In your pattern, when a match found, it will discard that event (e1 in your
scenario), so it won't get compared with other events. However, if you need
to hold that event and match it with more than a single event, then you can
use an event table as shown below.
@Plan:name('TestExecutionP
Hello WSO2 community.
I am trying to implement a siddhi query where 1 event in publisher can have
multiple event in subscriber. this fits well in pattern query but it looks
like it outputs as soon as 1 event is matched and there is no way to window
or tell the count.
here is the execution plan i
