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 <awanth...@wso2.com> 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 <sesh...@wso2.com> > 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 <awanth...@wso2.com> >> 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 > > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
