apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-2143) Evaluate and retire lib/math, lib/algo, and lib/streamquery operators
Date Thu, 01 Sep 2016 18:31:20 GMT

    [ https://issues.apache.org/jira/browse/APEXMALHAR-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

Mime
View raw message