[
https://issues.apache.org/jira/browse/NIFI-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966048#comment-15966048
]
ASF GitHub Bot commented on NIFI-3600:
--------------------------------------
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1595
From a first look the code seems ok but I have a quick question:
Do we truly need a permission denied relationship? It seems like a
deviation from the general nature of failure relationships (generally they are
nearly all encompassing).
Perhaps we could add the failure reason to an attribute and route to
failure?
Reason I ask is that I like the strong similarity between the *HDFS, the
*File and *S3 processors and I suspect this change would introduce change that
will move some of them appart?
> Improve logging and relationship routing for failures in DeleteHDFS
> -------------------------------------------------------------------
>
> Key: NIFI-3600
> URL: https://issues.apache.org/jira/browse/NIFI-3600
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Jeremy Dyer
> Assignee: Jeremy Dyer
>
> Currently if DeleteHDFS attempts to delete a file and does not have
> permissions to delete that file the flowfile session is rolled back and
> penalized. This causes the incoming connection into DeleteHDFS to build up
> over time and not process at all.
> This enhancement would add a new relationship to DeleteHDFS where files
> failures to delete a file strictly tied to invalid permissions would be
> routed given the end user the opportunity to react to those invalid
> permissions through another approach.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
