[
https://issues.apache.org/jira/browse/HBASE-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081414#comment-13081414
]
stack commented on HBASE-4180:
------------------------------
@Bochun
Can you rephrase this '0.21 does have isSecurityEnabled but not means it must
configured to use it.'? What is the difference between 0.20-SEC and 0.21?
HBase does not run on raw (non-secure) 0.21. It needs a few small patches to
do so. It will run on 0.22 and 0.23 non-secure. Until we figure otherwise,
we'd like to have it so the same hbase binary will run on 0.20-append, CDH3,
0.22, 0.23, MapR, etc. I've not looked at whats involved making hbase run
secure on all these versions (Gary is our man when it comes to that).
Hopefully we can make it so same hbase binary can run on all secure hadoop
combos (Will this be possible Gary?)
> 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
