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 "Stephen Chu (JIRA)" <ji...@apache.org> on 2014/10/24 18:03:34 UTC
[jira] [Updated] (HDFS-6741) Improve permission denied message when
FSPermissionChecker#checkOwner fails
[ https://issues.apache.org/jira/browse/HDFS-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Chu updated HDFS-6741:
------------------------------
Priority: Trivial (was: Minor)
Target Version/s: 3.0.0, 2.7.0 (was: 3.0.0, 2.6.0)
Labels: supportability (was: )
> Improve permission denied message when FSPermissionChecker#checkOwner fails
> ---------------------------------------------------------------------------
>
> Key: HDFS-6741
> URL: https://issues.apache.org/jira/browse/HDFS-6741
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 3.0.0, 2.5.0
> Reporter: Stephen Chu
> Assignee: Stephen Chu
> Priority: Trivial
> Labels: supportability
> Attachments: HDFS-6741.1.patch
>
>
> Currently, FSPermissionChecker#checkOwner throws an AccessControlException with a simple "Permission denied" message.
> When users try to set an ACL without ownership permissions, they'll see something like:
> {code}
> [schu@hdfs-vanilla-1 hadoop]$ hdfs dfs -setfacl -m user:schu:--- /tmp
> setfacl: Permission denied
> {code}
> It'd be helpful if the message had an explanation why the permission was denied to avoid confusion for users who aren't familiar with permissions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)