[
https://issues.apache.org/jira/browse/NIFI-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137145#comment-16137145
]
Bryan Bende commented on NIFI-4311:
-----------------------------------
The problem appears to be that we initialize the FileSystem object in
AbstractHadoopProcessor before we set the umask in the Configuration which
happens in the PutHDFS processor.
As part of initializing the FileSystem, the DFSClient stores the umask value at
that time, which is the original default value from hdfs-site.xml.
> PutHDFS not honoring umask property
> -----------------------------------
>
> Key: NIFI-4311
> URL: https://issues.apache.org/jira/browse/NIFI-4311
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
>
> Typically the hdfs-site.xml has a default umask of 022, which is prohibits
> write for group and other. So if you create a directory or file using the
> hadoop command line client, you'll get something like this by default:
> {code}
> drwxr-xr-x - bbende hdfs /test/foo
> {code}
> Now if you used PutHDFS and set the umask to 002, you would expect to
> prohibit write only for other and get rwxrwxr-x but you still get the same
> permissions as above from the default umask.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
