hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-9182) avoid FileSystem.getAclStatus rpc call for filesystems that don't support acl
Date Mon, 22 Dec 2014 22:50:13 GMT

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

Thejas M Nair commented on HIVE-9182:
-------------------------------------

I think the isExtendedAclEnabled check should also be replaced with above check. That call
is checking for dfs.namenode.acls.enabled configuration parameter which is not applicable
to all file systems.


> avoid FileSystem.getAclStatus rpc call for filesystems that don't support acl
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-9182
>                 URL: https://issues.apache.org/jira/browse/HIVE-9182
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.14.0
>            Reporter: Thejas M Nair
>            Assignee: Abdelrahman Shettia
>
> File systems such as s3, wasp (azure) don't implement Hadoop FileSystem acl functionality.
> Hadoop23Shims has code that calls getAclStatus on file systems.
> Instead of calling getAclStatus and catching the exception, we can also check FsPermission#getAclBit
.
> Additionally, instead of catching all exceptions for calls to getAclStatus and ignoring
them, it is better to just catch UnsupportedOperationException.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message