[
https://issues.apache.org/jira/browse/NIFI-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998827#comment-15998827
]
ASF GitHub Bot commented on NIFI-3600:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/1595
Reviewer consensus (see the Jira case for details) is to exclude the
hdfs.error.code for now, rather than possibly reporting an incorrect cause of
an IOException. Once we can tell the difference, we can add that attribute back
in. In that state, @bbende and I are a +1
Adding a unit test, removing the attribute, and merging to master. Thanks
much!
> 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
> Attachments: NIFI-3600_unit_test.patch
>
>
> 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)
