Hi Seshika, yes, as long as you are comparing against a constant it will work, but here since you are comparing against the event elements themselves, according to your equation I think you can get an event as below too,
[3714496353984310, Dehiwela, Nairobi, Dehiwela] correct me if I am wrong :) On Wed, Oct 29, 2014 at 1:24 PM, Seshika Fernando <[email protected]> wrote: > Well when we use counting patterns, we can have multiple occurrences of e1 > or e2. Refer, the last part of [1] > > 1. https://docs.wso2.com/display/CEP310/Patterns > > On Wed, Oct 29, 2014 at 1:21 PM, Awanthika Senarath <[email protected]> > wrote: > >> Hi Seshika, >> >> The problem seems to be involved with comparing more than two events for >> a pattern, I'm not much familiar with siddhi.. yet according to your logic >> you only check for >> e2 = Transaction[(e2.cardnum == e1.cardnum) and (e2.location != >> e1.location)] >> >> essentially your output will have a null event for the third location >> unless you take an e3 >> >> On Wed, Oct 29, 2014 at 1:16 PM, Seshika Fernando <[email protected]> >> wrote: >> >>> Thanks Awanthika. Once again, this defeats the purpose of having >>> counting patterns doesnt it? >>> >>> On Wed, Oct 29, 2014 at 1:12 PM, Awanthika Senarath <[email protected]> >>> wrote: >>> >>>> Hi Seshika, >>>> >>>> One work around you can do is check whether loc3 is null in an >>>> intermediate stream and insert it to FraudAlert. >>>> >>>> >>>> thanks and regards >>>> Awanthika >>>> >>>> >>>> -- >>>> Awanthika Senarath >>>> Software Engineer, WSO2 Inc. >>>> Mobile: +94717681791 >>>> >>>> >>>> >>> >> >> >> -- >> Awanthika Senarath >> Software Engineer, WSO2 Inc. >> Mobile: +94717681791 >> >> >> > -- Awanthika Senarath Software Engineer, WSO2 Inc. Mobile: +94717681791
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
