[
https://issues.apache.org/jira/browse/NIFI-12249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780639#comment-17780639
]
ASF subversion and git services commented on NIFI-12249:
--------------------------------------------------------
Commit 90498a352d059376b96630c1c3f1136313999d17 in nifi's branch
refs/heads/main from annanys23
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=90498a352d ]
NIFI-12249 FetchFTP and FetchSFTP set fetch.failure.reason on failures
- Set fetch.failure.reason to relationship name when routing to failure
relationships
This closes #7929
Signed-off-by: David Handermann <exceptionfact...@apache.org>
> FetchSFTP needs failure attributes
> ----------------------------------
>
> Key: NIFI-12249
> URL: https://issues.apache.org/jira/browse/NIFI-12249
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 2.0.0
> Reporter: Anna Nys
> Assignee: Anna Nys
> Priority: Minor
> Time Spent: 2h
> Remaining Estimate: 0h
>
> The FetchSFTP processor has several failure relationships:
> comms.failure
> not.found
> permission.denied
> While these relationships can help route files that fail for different
> reasons, it would be helpful to have the failure reason written to a flowfile
> attribute, so that the reason can be automatically included in an automated
> notification message.
> The value of the flowfile attribute could be used in an UpdateAttribute
> advanced rules to generate error-specific email notifications to the
> customer. Otherwise, we need separate processors for each failure
> relationship.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
