[
https://issues.apache.org/jira/browse/HBASE-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081415#comment-13081415
]
Gary Helmling commented on HBASE-4180:
--------------------------------------
As I said before, the presence of {{isSecurityEnabled}} is used to identify
*API* changes, not whether Hadoop is configured for Kerberos authentication.
We really don't care about the return value of {{isSecurityEnabled}}.
HBase does work with non-secure Hadoop, both 0.20 (pre-security) and
0.20-security (with hadoop.security.authentication=simple).
If there are API differences between {{UserGroupInformation}} in Hadoop 0.21
and 0.22+, we should account for those. Otherwise I still don't see what
exactly the issue is here. Are you encountering problems running on Hadoop
0.21 (which is not supported) that this is intended to solve?
> 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
