[ https://issues.apache.org/jira/browse/NIFI-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998830#comment-15998830 ]
ASF subversion and git services commented on NIFI-3600: ------------------------------------------------------- Commit 5f65b2561a25a10289a1a10c5325042ed988b105 in nifi's branch refs/heads/master from [~jeremy.dyer] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5f65b25 ] NIFI-3600 Improve logging and relationship routing for failures in DeleteHDFS realized that the session should be cloned here because its inside a for loop and the original flow file would be transferred but not be the latest flow file if an error occurred in the for loop @trixpan at a high level what do you think about this approach? NIFI-3600: Added unit test NIFI-3600: Removed the hdfs.error.code attribute Signed-off-by: Matt Burgess <mattyb...@apache.org> This closes #1595 > 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 > Fix For: 1.2.0 > > 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)