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

ASF GitHub Bot commented on APEXMALHAR-2139:
--------------------------------------------

GitHub user aayushia opened a pull request:

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

    APEXMALHAR-2139 

    Emit only the keys for which values changed or were added in a given window.

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

    $ git pull https://github.com/aayushia/apex-malhar APEXMALHAR-2139

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

    https://github.com/apache/apex-malhar/pull/338.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 #338
    
----
commit 7d36050d4602018b7f9b6cef563b01973b8ee5e6
Author: Aayushi Acharya <[email protected]>
Date:   2016-07-11T22:55:57Z

    APEXMALHAR-2139 #resolve #comment Emit only the keys for which values 
changed or were added in a given window.

----


> UniqueCounter changes
> ---------------------
>
>                 Key: APEXMALHAR-2139
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2139
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>            Reporter: Aayushi Acharya
>             Fix For: 3.5.0
>
>
> 1.Update the unique counter operator from Malhar 
> https://github.com/apache/apex-malhar/blob/master/library/src/main/java/com/datatorrent/lib/algo/UniqueCounter.java
>  to emit one tuple at a time vs dumping a map.
> 2.Emit only the keys for which values changed or were added in a given window.
> 3.Add test cases for 1 and 2.



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

Reply via email to