[
https://issues.apache.org/jira/browse/HBASE-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081417#comment-13081417
]
Gary Helmling commented on HBASE-4180:
--------------------------------------
@Bochun
{quote}
0.21 API incompatible is problem for downstream projects.
Hive extracts a shims components for this.
Will HBase consider some similar changes?
{quote}
This is the purpose of the {{User}} class -- to isolate the UGI changes. See
{{User.HadoopUser}} and {{User.SecureHadoopUser}}. If we need to add a
separate version for Hadoop 0.21, we can do that, but as Stack mentions there
are other, non-related problems with running on Hadoop 0.21.
> 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
