You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streams.apache.org by "Matt Franklin (JIRA)" <ji...@apache.org> on 2014/06/26 21:09:24 UTC
[jira] [Commented] (STREAMS-80) StreamsProcressorTask and
StreamsPersistWriterTask are BROKEN
[ https://issues.apache.org/jira/browse/STREAMS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045022#comment-14045022 ]
Matt Franklin commented on STREAMS-80:
--------------------------------------
This can be closed right?
> 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)