[
https://issues.apache.org/jira/browse/HADOOP-14730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114958#comment-16114958
]
Chris Douglas commented on HADOOP-14730:
----------------------------------------
bq. hadoop-azure-datalake.jar with Patch 003 would not link to Hadoop 2.x
common jar
This is an unusual requirement. Attached v004 which should link against 2.x.
bq. Any reason to prefer Patch 003 over 002? Considering FSPermission.getAclBit
is deprecated.
Just in case applications rely on this field, presumably. HDFS-6984 preserved
this for HDFS, but not for ADLS.
I'm ambivalent among v002-v004.
> hasAcl property always set to false, regardless of FsPermission higher bit
> order
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-14730
> URL: https://issues.apache.org/jira/browse/HADOOP-14730
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.0.0-beta1
> Reporter: Vishwajeet Dusane
> Assignee: Chris Douglas
> Fix For: 3.0.0-beta1
>
> Attachments: HADOOP-14730.001.patch, HADOOP-14730.002.patch,
> HADOOP-14730.003.patch, HADOOP-14730.004.patch
>
>
> 2 Unit Test cases are failing [Azure-data-lake Module
> |https://github.com/apache/hadoop/blob/4966a6e26e45d7dc36e0b270066ff7c87bcd00cc/hadoop-tools/hadoop-azure-datalake/src/test/java/org/apache/hadoop/fs/adl/TestGetFileStatus.java#L44-L44],
> caused after HDFS-6984 commit.
> Issue seems to be {{hasAcl}} is hard coded to {{false}}.
> {code:java}
> public FileStatus(long length, boolean isdir,
> int block_replication,
> long blocksize, long modification_time, long access_time,
> FsPermission permission, String owner, String group,
> Path symlink,
> Path path) {
> this(length, isdir, block_replication, blocksize, modification_time,
> access_time, permission, owner, group, symlink, path,
> false, false, false);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
