[jira] [Updated] (HDFS-4319) FSShell copyToLocal creates files with the executable bit set

["Brahma Reddy Battula (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brahma Reddy Battula updated HDFS-4319:
---------------------------------------
    Target Version/s: 3.4.0  (was: 3.3.0)

Bulk update: moved all 3.3.0 non-blocker issues, please move back if it is a blocker.



> FSShell copyToLocal creates files with the executable bit set
> -------------------------------------------------------------
>
>                 Key: HDFS-4319
>                 URL: https://issues.apache.org/jira/browse/HDFS-4319
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.3-alpha
>            Reporter: Colin McCabe
>            Priority: Minor
>
> With the default value of {{fs.permissions.umask-mode}}, {{022}},  {{FSShell copyToLocal}} creates files with the executable bit set.
> If, on the other hand, you change {{fs.permissions.umask-mode}} to something like {{133}}, you encounter a different problem.  When you use {{copyToLocal}} to create directories, they don't have the executable bit set, meaning they do not have search permission.
> Since HDFS doesn't allow the executable bit to be set on files, it seems illogical to add it in when using {{copyToLocal}}.  This is also a regression, since branch 1 did not have this problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org