[
https://issues.apache.org/jira/browse/NIFI-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966057#comment-15966057
]
ASF GitHub Bot commented on NIFI-3600:
--------------------------------------
Github user jdye64 commented on the issue:
https://github.com/apache/nifi/pull/1595
My reasoning for adding the extra relationship was for end users to
understand that certain directories or files had improper permissions and have
a visible way to see that with the extra relationship. However your right we
could just add something like a "error.code" and "error.message" attributes and
route to failure. I would like the "error.code" for sure however since that
would be easy to route against while error.message might contain different
messages from the exceptions when dependency versions change
> 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)
