[
https://issues.apache.org/jira/browse/HADOOP-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590627#action_12590627
]
Raghu Angadi commented on HADOOP-3186:
--------------------------------------
Can you describe what the permission checking policy for rename() is?
"-mv" is implemented by rename but not correctly. "mv file /dest" creates
/dest/file if dest is a directly. but "rename(file, /dest)", will either fail
or create /dest but will not /dest/file, right?
> Incorrect permission checking on mv
> ------------------------------------
>
> Key: HADOOP-3186
> URL: https://issues.apache.org/jira/browse/HADOOP-3186
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.16.2
> Environment: permission turned on
> Reporter: Koji Noguchi
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: 3186_20080418b.patch
>
>
> {noformat}
> /data <dir> 2008-04-04 00:47 rwxr-xr-x root users
> /data/testdir <dir> 2008-04-04 23:44 rwxrwxrwx
> knoguchi users
> /user/knoguchi/test <dir> 2008-04-04 23:45 rwxrwxrwx
> knoguchi users
> [knoguchi]$ hadoop dfs -mv /user/knoguchi/test /data/testdir
> mv: org.apache.hadoop.fs.permission.AccessControlException: Permission
> denied: user=knoguchi, access=WRITE, inode="data":root:users:rwxr-xr-x
> {noformat}
> Since target directory, /data/testdir, exists, it should not check the
> permission of the parent directory
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
