You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Paul Grey (Jira)" <ji...@apache.org> on 2021/09/27 13:53:00 UTC
[jira] [Commented] (NIFI-9235) Improve PutHDFS documentation;
detection of umask / HDFS default ACL conflict
[ https://issues.apache.org/jira/browse/NIFI-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420757#comment-17420757 ]
Paul Grey commented on NIFI-9235:
---------------------------------
After discussing with others, the recommendation is that the `put` operation should fail, if the umask conflict is detected. PutHDFS should not write to the remote endpoint if the write would result in a file with a less restrictive permission set than is intended.
> Improve PutHDFS documentation; detection of umask / HDFS default ACL conflict
> -----------------------------------------------------------------------------
>
> Key: NIFI-9235
> URL: https://issues.apache.org/jira/browse/NIFI-9235
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.13.2
> Reporter: Paul Grey
> Assignee: Paul Grey
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The PutHDFS processor specifies a umask configuration property, which is intended to contribute to the permissions of files it writes to HDFS. If the PutHDFS target folder specifies a default ACL in the HDFS configuration, the PutHDFS umask is ignored.
> Improve PutHDFS documentation to call out this issue, and investigate means of alerting the user to this situation when it is detected at run time.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)