You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2016/07/15 21:34:20 UTC

[jira] [Commented] (HIVE-13990) Client should not check dfs.namenode.acls.enabled to determine if extended ACLs are supported

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

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

[~cnauroth] Are there any new apis that might help in checking if ACL is enabled in the FS ?


> 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)