[jira] [Updated] (NIFI-5719) FetchFile can fail to move original file on completion but still route to success
[ https://issues.apache.org/jira/browse/NIFI-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5719: -- Fix Version/s: 1.8.0 > 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 > Fix For: 1.8.0 > > > 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)
[jira] [Updated] (NIFI-5719) FetchFile can fail to move original file on completion but still route to success
[ https://issues.apache.org/jira/browse/NIFI-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-5719: Fix Version/s: (was: 1.8.0) I just noticed that 1.8.0 RC is already created. Clearing fix version. > 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)
[jira] [Updated] (NIFI-5719) FetchFile can fail to move original file on completion but still route to success
[ https://issues.apache.org/jira/browse/NIFI-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-5719: Resolution: Fixed Fix Version/s: 1.8.0 Status: Resolved (was: Patch Available) > 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 > Fix For: 1.8.0 > > > 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)
[jira] [Updated] (NIFI-5719) FetchFile can fail to move original file on completion but still route to success
[ https://issues.apache.org/jira/browse/NIFI-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende updated NIFI-5719: -- Status: Patch Available (was: Open) > 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)