[
https://issues.apache.org/jira/browse/NIFI-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235899#comment-16235899
]
Matt Burgess commented on NIFI-4559:
------------------------------------
I'm about to submit a PR implementing #2 above. Current behavior does not
change if Output Destination Attribute is set (i.e. all flow files go to
'original' and are not penalized regardless of the setting of the new "Penalize
Non-zero Status" property, the doc reflects that). Also current behavior when
output is in flowfile content (i.e. Output Destination Attribute is not set) is
retained via default settings, except that the user will need to route the
'nonzero status' relationship to the same downstream processor as the 'output
stream' relationship.
> ExecuteStreamCommand should have a failure relationship
> -------------------------------------------------------
>
> Key: NIFI-4559
> URL: https://issues.apache.org/jira/browse/NIFI-4559
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.4.0
> Reporter: Joseph Witt
> Assignee: Matt Burgess
> Priority: Major
>
> ExecuteStreamCommand only has a success relationship. The gist is it
> executes the command, captures the output stream, code, etc.. and stores the
> necessary content and attributes.
> However, for those wanting to see the status code as an indicator of failure
> they have to create a flow which checks, loops, etc.. This is more work than
> necessary since the processor can provide a better indicator. By adding a
> failure relationship we can route results and status codes for non-zero to
> this relationship. We'll have to consider backward compatibility friendly
> ideas but the gist is to make this common failure/retry pattern easier to
> configure and track.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
