[
https://issues.apache.org/jira/browse/HIVE-13990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382878#comment-15382878
]
Chris Nauroth commented on HIVE-13990:
--------------------------------------
[~thejas], is this possibly a duplicate of HIVE-9182? There was an uncommitted
patch on that one. During code review for that patch, I gave feedback that you
can avoid {{getAclStatus}} calls by checking {{FsPermission#getAclBit}}. For
any {{FileSystem}} that doesn't implement ACLs, the ACL bit will always be
false. I expect this would work for all {{FileSystem}} implementations and
avoid tight coupling to HDFS server-side configuration. I think the same
feedback applies here.
> Client should not check dfs.namenode.acls.enabled to determine if extended
> ACLs are supported
> ---------------------------------------------------------------------------------------------
>
> Key: HIVE-13990
> URL: https://issues.apache.org/jira/browse/HIVE-13990
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
> Affects Versions: 1.2.1
> Reporter: Chris Drome
> Assignee: Chris Drome
> Attachments: HIVE-13990-branch-1.patch, HIVE-13990.1-branch-1.patch,
> HIVE-13990.1.patch
>
>
> dfs.namenode.acls.enabled is a server side configuration and the client
> should not presume to know how the server is configured. Barring a method for
> querying the NN whether ACLs are supported the client should try and catch
> the appropriate exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
