You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2016/06/11 01:42:21 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=15325627#comment-15325627 ]
Ashutosh Chauhan commented on HIVE-13990:
-----------------------------------------
Usual practice is to first commit on master and then do backports. Would you like to put up a patch against master?
> 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
> Attachments: HIVE-13990-branch-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)