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

Haohui Mai commented on HDFS-6326:
----------------------------------

bq. The current FsPermission#fromShort(short) appears to discard upper bits 
other than the sticky bit.

This is dangerous as in general many clients assumes that the permission is in 
000~1777. Violating this assumption can be problematic. See my comments in 
HDFS-5923 for details.

bq. This worries me even more than ls -R!! Distcp-ing large directories with no 
ACLs just became 2X expensive.

distcp won't call {{getAclStatus()}} at all expect the user specifies -p, which 
requires a call to {{getAclStatus()}} anyway. I don't see why distcp is more 
expensive than before.

> WebHdfs ACL compatibility is broken
> -----------------------------------
>
>                 Key: HDFS-6326
>                 URL: https://issues.apache.org/jira/browse/HDFS-6326
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: Daryn Sharp
>            Assignee: Chris Nauroth
>            Priority: Blocker
>         Attachments: HDFS-6326.1.patch, HDFS-6326.2.patch
>
>
> 2.4 ACL support is completely incompatible with <2.4 webhdfs servers.  The NN 
> throws an {{IllegalArgumentException}} exception.
> {code}
> hadoop fs -ls webhdfs://nn/
> Found 21 items
> ls: Invalid value for webhdfs parameter "op": No enum constant 
> org.apache.hadoop.hdfs.web.resources.GetOpParam.Op.GETACLSTATUS
> [... 20 more times...]
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to