[ https://issues.apache.org/jira/browse/HDFS-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184916#comment-14184916 ]
Harsh J commented on HDFS-6741: ------------------------------- Many thanks for the patch here! Could you take the cue from my duplicated patch over at HDFS-7292, and change the user and inode into the more standard user= and inode= formats? We may also just print the inode object as-is, cause it carries a lot of other informational items at its tail automatically. I also added simple regression-catching changes at a couple places in the tests in HDFS-7292; having some of those would be beneficial as well - just in case. > 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)