Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 9 Aug 2011 03:20:27 +0000 (UTC)
From: "Gary Helmling (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1619512468.18795.1312860027226.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <6403386.18685.1312856067542.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4180) HBase should check the
 isSecurityEnabled flag
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gary Helmling commented on HBASE-4180:
--------------------------------------

So is the issue here that we're not correctly accounting for {{UserGroupInformation}} API changes between Hadoop 0.21 and 0.22+?

> HBase should check the isSecurityEnabled flag
> ---------------------------------------------
>
>                 Key: HBASE-4180
>                 URL: https://issues.apache.org/jira/browse/HBASE-4180
>             Project: HBase
>          Issue Type: Bug
>          Components: security
>            Reporter: Bochun Bai
>            Assignee: Bochun Bai
>         Attachments: HBASE-4180.patch
>
>
> Hadoop 0.21.0's UserGroupInfomation support the security check flag and always returns false.
> HBase should check both the method existence and the return value.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira