Hi David,
Thanks for the inputs.
I did not choose to do so because of following currently identified reasons:
1. lib.util.FilterOperator is actually not an operator instead it is an
abstract class
- Does not evaluate any expression/condition
- Requires an concrete implementation and specifical
Hi,
It would be useful if you could state why the existing FilterOperator in
Malhar does not satisfy your use case.
The existing operator is at
library/src/main/java/com/datatorrent/lib/util/FilterOperator.java.
David
On Sat, May 7, 2016 at 2:34 PM, Pradeep A. Dalvi wrote:
> Dear Folks,
>
> We
Dear Folks,
I've filed following JIRA for this:
https://issues.apache.org/jira/browse/APEXMALHAR-2082
Thanks,
Pradeep A. Dalvi
On Mon, May 9, 2016 at 9:42 PM, Pradeep A. Dalvi wrote:
> Mea Culpa! Yes. An error is certainly considered. I forgot to mention in
> the proposal.
>
> Thanks,
> Pradee
Mea Culpa! Yes. An error is certainly considered. I forgot to mention in
the proposal.
Thanks,
Pradeep A. Dalvi
On Mon, May 9, 2016 at 6:05 PM, Sandeep Deshmukh
wrote:
> + 1
>
> An error port can be added to redirect tuples for which expression
> evaluation failed.
>
> Regards,
> Sandeep
>
> On
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
eff
+ 1
An error port can be added to redirect tuples for which expression
evaluation failed.
Regards,
Sandeep
On Mon, May 9, 2016 at 6:02 PM, Shubham Pathak
wrote:
> + 1 for having a filter operator.
>
> Thanks,
> Shubham
>
> On Sun, May 8, 2016 at 10:50 AM, Mohit Jotwani
> wrote:
>
> > +1
> >
>
+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 wrote:
> +1
>
> Regards,
> Mohit
> On 8 May 2016 03:04, "Pradeep A. Dalvi" wrote:
>
> > Dear Folks,
> >
> > We are working on Filter Operator whic
+ 1 for having a filter operator.
Thanks,
Shubham
On Sun, May 8, 2016 at 10:50 AM, Mohit Jotwani
wrote:
> +1
>
> Regards,
> Mohit
> On 8 May 2016 03:04, "Pradeep A. Dalvi" wrote:
>
> > Dear Folks,
> >
> > We are working on Filter Operator which will allow apex users to filter
> > (select/drop)
+1
Regards,
Mohit
On 8 May 2016 03:04, "Pradeep A. Dalvi" 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 tupl
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/f
10 matches
Mail list logo