[NIFI-7041] PutSFTP 1.10 results in zero permissions on destination by default

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0
• Fix Version/s: 1.11.0
• Component/s: Core Framework
• Assignee: Joe Witt
• Reporter: James Ignatius
• Created: 17/Jan/20 18:51
• Updated: 19/Jan/20 13:50
• Resolved: 19/Jan/20 13:49

Description

Recently updated our NiFi environments from 1.8 to 1.10. Issue occurs with PutSFTP 1.10 processors. If the Permissions property is left blank, the file is put with no permissions. In previous releases, and according to the nifi docs, if the permissions are left blank it should default to the original permissions. 

Sample file put using PutSFTP 1.10:
---------- 1 9542 9544 1788 Jan 13 20:59 Test-2018-05-13-2018-05-19.zip
The workaround is obviously to be sure and set the octal number for permissions, though if you forget, you can end up with thousands of unpermissioned files which require root to delete or re-permission. 

Sometimes the file errors, and sometimes it does not. I have observed this error in the app log on some of the files:
Failure java.io.IOException: Failed to rename dot-file to /data/incoming/OSDM_CORE_aplgenff010_20200115140000.zip due to 4: Failure
at org.apache.nifi.processors.standard.util.SFTPTransfer.put(SFTPTransfer.java:766)

Issue Links

• links to: GitHub Pull Request #4000