You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Binglin Chang (JIRA)" <ji...@apache.org> on 2012/12/20 06:33:12 UTC

[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid

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

Binglin Chang updated HDFS-4325:
--------------------------------

          Component/s: namenode
                       hdfs-client
    Affects Version/s: 2.0.3-alpha
                       3.0.0
        Fix Version/s: 2.0.3-alpha
    
> ClientProtocol.createSymlink parameter dirPerm invalid
> ------------------------------------------------------
>
>                 Key: HDFS-4325
>                 URL: https://issues.apache.org/jira/browse/HDFS-4325
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client, namenode
>    Affects Versions: 3.0.0, 2.0.3-alpha
>            Reporter: Binglin Chang
>             Fix For: 2.0.3-alpha
>
>
> {code}
>    * @param link The path of the link being created.
>    * @param dirPerm permissions to use when creating parent directories
>    * @param createParent - if true then missing parent dirs are created
>    *                       if false then parent must exist
> {code}
> According to javadoc, auto created parent dir's permissions will be dirPerm, but in fact directory permissions are always inherit from parent directory plus u+wx.
> IMHO, createSymlink behavior should be the same as create, which also inherit parent dir permission, so the current behavior makes sense, but the related dirPerm parameters should be removed cause it is invalid and confusing. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira