[ https://issues.apache.org/jira/browse/NIFI-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045224#comment-17045224 ]
Josef Zahner commented on NIFI-6883: ------------------------------------ This issue has been fixed in 1.11.x. I can't remember the Jira number . > PutSFTP Permissions Wrong with NiFi 1.10.0 > ------------------------------------------ > > Key: NIFI-6883 > URL: https://issues.apache.org/jira/browse/NIFI-6883 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.10.0 > Environment: OpenJDK 8, Centos 7.6, NiFi Cluster with 2 Nodes > Reporter: Josef Zahner > Priority: Major > Attachments: Canvas Overview.png, Flowfile Permissions.png, PutSFTP > Config.png > > > The PutSFTP processor doesn't anymore respect the flowfile attribute > "file.permissions". It sets per default always "000" if the field > "Permissions" from PutSFTP is empty, even thought the attribute has been set > by the ListSFTP. Occurs since NiFi 1.10.0. > *Workaround*: set the permission manually by writing them into field > "Permissions". > *Steps to reproduce*: Check my canvas overview picture below with ListSFTP, > FetchSFTP, UpdateAttribute & PutSFTP processors. As input I've used the > "testfile.txt" and as output I've written "newname.txt". Permissions for the > output are "----------" instead of "664". > {code:java} > /tmp/my_test: > total 4.0K > drwxrwxr-x 2 usera usera 26 Nov 19 09:40 . > drwxrwxrwt. 10 root root 203 Nov 19 10:03 .. > -rw-rw-r-- 1 usera usera 4 Nov 19 09:40 testfile.txt{code} > {code:java} > /tmp/my_test_out: > total 4.0K > drwxrwxr-x 2 usera usera 25 Nov 19 10:03 . > drwxrwxrwt. 10 root root 203 Nov 19 10:03 .. > ---------- 1 usera usera 4 Nov 19 10:03 newname.txt > {code} > Canvas Overview: > !Canvas Overview.png|width=521,height=683! > > Flowfile Permission before PutSFTP: > !Flowfile Permissions.png|width=699,height=521! > PutSFTP Config for field "Permissions" (default empty) > !PutSFTP Config.png|width=788,height=547! -- This message was sent by Atlassian Jira (v8.3.4#803005)