[
https://issues.apache.org/jira/browse/HBASE-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081392#comment-13081392
]
Gary Helmling commented on HBASE-4180:
--------------------------------------
-1 on the patch
{{User.IS_SECURE_HADOOP}} is a private variable used to differentiate between
the API incompatible changes to {{UserGroupInformation}} between Hadoop 0.20
and 0.21+. The API-incompatible methods are accommodated using reflection so
that we're not compile-time bound to Hadoop 0.21+. Whether
hadoop.security.authentication is set to "simple" or "kerberos" (which is what
{{isSecurityEnabled()}} returns) makes no difference to accounting for the API
changes.
Can you describe more of the underlying problem that you're observing that this
patch is intended to fix?
> 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
