[ https://issues.apache.org/jira/browse/NIFI-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654670#comment-16654670 ]
ASF subversion and git services commented on NIFI-5719: ------------------------------------------------------- Commit f3f7cdbab9248ba13c00d0e27a398e820e9ec7ed in nifi's branch refs/heads/master from [~bbende] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f3f7cdb ] NIFI-5719 Ensuring FetchFile routes to failure if the move completion strategy can't be completed This closes #3088. Signed-off-by: Koji Kawamura <ijokaruma...@apache.org> > FetchFile can fail to move original file on completion but still route to > success > --------------------------------------------------------------------------------- > > Key: NIFI-5719 > URL: https://issues.apache.org/jira/browse/NIFI-5719 > Project: Apache NiFi > Issue Type: Bug > Affects Versions: 1.7.1 > Reporter: Bryan Bende > Assignee: Bryan Bende > Priority: Minor > > Currently before fetching the file there are some checks to ensure that the > completion strategy will succeed. The check for the move strategy ensures > that if the target directory exists that it is a directory and is writable. > The issue is that if the directory does not exist, then later during the > actual move we try to create it, but this could fail, primarily due to the > parent directory not being writable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)