There are few operators meant to perform certain specific operations and optionally based on certain condition. However, I think, it makes sense to have condition/expression evaluation as a separate operator and not as a part of every other operator whose primary objective is something else. So effectively this operator would help remove/reduce redundant condition/expression evaluation code from some such operators.
Thanks, Pradeep A. Dalvi On Mon, May 9, 2016 at 6:04 PM, Yogi Devendra <[email protected]> wrote: > +1 for the idea. But, just wanted to know if it overlaps with any of the > existing operators in malhar. > > ~ Yogi > > On 8 May 2016 at 10:50, Mohit Jotwani <[email protected]> wrote: > > > +1 > > > > Regards, > > Mohit > > On 8 May 2016 03:04, "Pradeep A. Dalvi" <[email protected]> wrote: > > > > > Dear Folks, > > > > > > We are working on Filter Operator which will allow apex users to filter > > > (select/drop) tuples based on the certain condition from incoming > stream. > > > > > > > > > Use case: > > > > > > ------------- > > > > > > In many cases, not all tuples are of interest for the downstream > > operators. > > > In such cases, one may want select/filter out tuples to downstream. > Also > > > one may want to process tuples which did not meet the > > condition/expression. > > > > > > > > > Functionality: > > > > > > ----------------- > > > > > > 1. Filter operator shall receive POJO as input tuple and emit POJO on > > > either of output ports i.e. true and false. As the output ports' name > > > signify, when condition is met then the POJO shall be emitted on true > > port > > > and if condition is not met then that POJO shall be emitted on false > > port. > > > > > > 2. Operator needs condition/expression as a input param. This condition > > is > > > based on expression language support we already have in Malhar. > > > > > > > > > Please feel free to let me know your thoughts on this. > > > > > > > > > Thanks, > > > > > > -- > > > Pradeep A. Dalvi > > > > > >
