[jira] [Commented] (APEXMALHAR-2143) Evaluate and retire lib/math, lib/algo, and lib/streamquery operators

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456254#comment-15456254
 ] 

ASF GitHub Bot commented on APEXMALHAR-2143:


Github user asfgit closed the pull request at:

https://github.com/apache/apex-malhar/pull/389


> Evaluate and retire lib/math, lib/algo, and lib/streamquery operators
> -
>
> Key: APEXMALHAR-2143
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2143
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: David Yan
>Assignee: Velineni Lakshmi Prasanna
>
> The operators in these 3 packages were developed in the early stages of the 
> product and we need to evaluate and assess them to see if there are 
> redundancies, bugs and look at the usability.
> Pramod's suggestion is that we go through the operators in those packages on 
> an
> individual basis and grade them into 3 buckets, those that meet the level
> we expect from the operators (could be few of them), those that are
> potentially useful but need additional work and those that we don't think
> would be useful. The ones in the first bucket can remain in place, the
> second set can be moved to malhar-misc and third set moved to malhar-misc and 
> deprecated.
> Please also track the individual operator in a shared Google spreadsheet.
> Note that the operators in lib/streamquery does not need to be individually 
> evaluated since it is really one unit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (APEXMALHAR-2143) Evaluate and retire lib/math, lib/algo, and lib/streamquery operators

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456108#comment-15456108
 ] 

ASF GitHub Bot commented on APEXMALHAR-2143:


GitHub user prasannapramod reopened a pull request:

https://github.com/apache/apex-malhar/pull/389

APEXMALHAR-2143 - Evaluate and retire lib/math, lib/algo, and 
lib/streamquery operators

@davidyan74 @PramodSSImmaneni @tweise  please review . I am working on 
fixing the functionality of the operators like "BottomNUniqueMap" , 
"InsertSort", "TopN", "UniqueCounter", "MarginKeyVal" . Also, I am planning to 
reimplement some operators like "BottomNMap" using the windows operator and 
managed state .

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/prasannapramod/apex-malhar ApexMalhar-2143

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/apex-malhar/pull/389.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #389


commit 8f00cefa2a14756a65e0baad48db0d52e2fe66a3
Author: Lakshmi Prasanna Velineni 
Date:   2016-08-25T03:54:53Z

Updated algo & working on math operators




> Evaluate and retire lib/math, lib/algo, and lib/streamquery operators
> -
>
> Key: APEXMALHAR-2143
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2143
> Project: Apache Apex Malhar
>  Issue Type: Task
>Reporter: David Yan
>Assignee: Velineni Lakshmi Prasanna
>
> The operators in these 3 packages were developed in the early stages of the 
> product and we need to evaluate and assess them to see if there are 
> redundancies, bugs and look at the usability.
> Pramod's suggestion is that we go through the operators in those packages on 
> an
> individual basis and grade them into 3 buckets, those that meet the level
> we expect from the operators (could be few of them), those that are
> potentially useful but need additional work and those that we don't think
> would be useful. The ones in the first bucket can remain in place, the
> second set can be moved to malhar-misc and third set moved to malhar-misc and 
> deprecated.
> Please also track the individual operator in a shared Google spreadsheet.
> Note that the operators in lib/streamquery does not need to be individually 
> evaluated since it is really one unit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)