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

ASF GitHub Bot commented on STREAMS-80:
---------------------------------------

GitHub user rbnks opened a pull request:

    https://github.com/apache/incubator-streams/pull/15

    Fixed bug for STREAMS-80

    Fixed bug that would cause processors and writers to end execution early 
and orphan data.  Bug was introduced in a recent commit.

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

    $ git pull https://github.com/rbnks/incubator-streams STREAMS-80

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

    https://github.com/apache/incubator-streams/pull/15.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 #15
    
----
commit 00a2a27766788c92698ae91a9f128f253aaa9891
Author: rebanks <[email protected]>
Date:   2014-05-15T18:39:10Z

    Fixed bug for STREAMS-80

----


> StreamsProcressorTask and StreamsPersistWriterTask are BROKEN
> -------------------------------------------------------------
>
>                 Key: STREAMS-80
>                 URL: https://issues.apache.org/jira/browse/STREAMS-80
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Ryan Ebanks
>            Priority: Critical
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> A recent commit seems to have introduced this.  Its a simple fix, but the 
> while statement on line 70 of StreamsProviderTask should read
> while(this.keepRunning.get() || datum != null) {
> And line 75 in StreamsPersist writer task should read
> while(this.keepRunning.get() || datum != null) {
> Both lines are missing the datum != null statement.  This causes tasks to be 
> shutdown before data is processed and data is orphaned in the stream.  In the 
> worst case only the provider runs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to