hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid
Date Sat, 02 May 2015 04:32:14 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524686#comment-14524686
] 

Hadoop QA commented on HDFS-4325:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply the patch during
dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12594139/HDFS-4325.v1.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/10558/console |


This message was automatically generated.

> 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: 2.0.4-alpha
>            Reporter: Binglin Chang
>            Assignee: Binglin Chang
>         Attachments: HDFS-4325.v1.patch
>
>
> {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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message