[Dev] pattern for one to many match or multi match events ?

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

Re: [Dev] pattern for one to many match or multi match events ?

; > > -- Option 1 > > from subscriber[publisherTable.pid == pid in publisherTable] >> select pid, time >> insert into AlertStream1; > > > > -- Option 2 >> from subscriber as s join publisherTable as p >> on p.pid == s.pid >> select p.pid, s.sid, s.time &

Re: [Dev] pattern for one to many match or multi match events ?

table publisherTable (pid string, time string); >>> >>> >>>> from publisher >>>> insert into publisherTable; >>> >>> >>> >>> -- Option 1 >>> >>> from subscriber[publisherTable.pid == pid in publisherTable] &g

[Dev] [Siddhi] non-matched or expired events in pattern query

Hi, is there a way to get events that didnt match within the given time frame. for example: define stream publisher (pid string, time string); define stream subscriber (pid string, sid string, time string); from every (e1=publisher) -> e2=subscriber[e1.pid == pid] within 10 sec select e1.pid, e

Re: [Dev] [Siddhi] non-matched or expired events in pattern query

nto not_seen_in_last_10_sec_events; > > > Moreover, I didn't get what you meant by "also is there a way to perform > intersection of events based on grouping or time window ?" can you please > elaborate on this? > > Regards, > > On Mon, Sep 25, 2017 at 11:02

Re: [Dev] [Siddhi] non-matched or expired events in pattern query

sorry bit correction on the following line in *BOLD*. .now i want to catch if certain jobs (publish -> subscribe) has *NOT* been finished with 10 sec. On Tue, Sep 26, 2017 at 7:05 PM, Jayesh Senjaliya wrote: > Hi Grainier, > > ya, i came across that example page, but i think t

Re: [Dev] [Siddhi] non-matched or expired events in pattern query

tion. So you > can find more details about absent pattern at [1] > > Still, Siddhi 4 is not production ready so I wonder whether you can use > this feature or not. > > [1] http://www.javahelps.com/2017/08/detect-absence-of-events- > wso2-siddhi.html > > > > > On Tu

Re: [Dev] [Siddhi] non-matched or expired events in pattern query

>> from jobsCompletedInTime >> delete jobTable >> on jobTable.pid == pid and jobTable.sid == sid; > > >> -- so if we join expiredPublisherEvents with the jobTable, the result >> will be the jobs that are not completed within time > > from expiredPublisherE