[jira] [Comment Edited] (NIFI-528) Add support to specify a timeout on ExecuteStreamCommand, ExecuteScript, and ExecuteProcess

["Mike Drob (JIRA)" <ji...@apache.org>]

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

Mike Drob edited comment on NIFI-528 at 4/20/15 9:14 PM:
---------------------------------------------------------

I don't think it would be a minor case... I imagine a failure indicating something like malformed data, while a timeout could indicate network issues or other transient issues.

Edit: To clarify, it seems easier to go from two relationships to one where you don't care about the distinction than from one to two when you do.


was (Author: mdrob):
I don't think it would be a minor case... I imagine a failure indicating something like malformed data, while a timeout could indicate network issues or other transient issues.

> Add support to specify a timeout on ExecuteStreamCommand, ExecuteScript, and ExecuteProcess 
> --------------------------------------------------------------------------------------------
>
>                 Key: NIFI-528
>                 URL: https://issues.apache.org/jira/browse/NIFI-528
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Michael Wagner
>              Labels: beginner, processor
>
> Should be a way to specify a timeout on ExecuteStreamCommand, ExecuteScript, and ExecuteProcess. If the script hung for some reason, kill the process and move on, send the timeout flowfile to a failure route. 



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