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

Andrew Purtell commented on HBASE-7066:
---------------------------------------

bq. Have we ever considered making security first class in 0.96 (not a 
coprocessor, though still switchable)?

I'm not in favor of this approach unless we want HBASE-6222, specifically the 
KV labeling part, in which case the changes are so invasive anyway we might as 
well move everything into core and furthermore reimplement access control on 
top of labeling.

bq. Change stopMaster() and shutdown() signature with "throws 
AccessDeniedException"

I think it will be a little weird to have these two methods throw a more 
specific signature than IOE where everywhere else we have IOE. The larger issue 
of (ab)use of IOE is a major refactoring. Also, I think AccessDeniedException 
should remain in the security package until security is otherwise not 
encapsulated there.


                
> Some HMaster coprocessor exceptions are being swallowed in try catch blocks
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-7066
>                 URL: https://issues.apache.org/jira/browse/HBASE-7066
>             Project: HBase
>          Issue Type: Bug
>          Components: Coprocessors, security
>    Affects Versions: 0.94.2, 0.96.0
>            Reporter: Francis Liu
>            Assignee: Francis Liu
>            Priority: Critical
>         Attachments: HBASE-7066_94.patch, HBASE-7066_trunk.patch, 
> HBASE-7066_trunk.patch
>
>
> This is causing HMaster.shutdown() and HMaster.stopMaster() to succeed even 
> when an AccessDeniedException is thrown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to