hive-issues 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-13990) Client should not check dfs.namenode.acls.enabled to determine if extended ACLs are supported
Date Fri, 15 Jul 2016 21:40:20 GMT

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

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

At the very least, I think we should cache the information that ACL is not supported after
the UnsupportedException is thrown. Otherwise, it could end up being very expensive to deal
with that exception for every file check.


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

Mime
View raw message