[
https://issues.apache.org/jira/browse/HBASE-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579989#comment-14579989
]
Mikhail Antonov commented on HBASE-13755:
-----------------------------------------
Good point. I actually just left these IOExceptions in place mostly to avoid
having to modify callers which catch IOExceptions.
I can definitely remove IOException from isSuperUser() method and replace it
with illegalstateexception. In initialize() method, we have User.getCurrent()
call inside, which throws IOException anyway.. not sure it'd good idea to catch
it and re-translate to something else. Should we leave IOException in
initialize() method and replace in isSuperUser()?
> Provide single super user check implementation
> ----------------------------------------------
>
> Key: HBASE-13755
> URL: https://issues.apache.org/jira/browse/HBASE-13755
> Project: HBase
> Issue Type: Improvement
> Reporter: Anoop Sam John
> Assignee: Mikhail Antonov
> Fix For: 2.0.0, 1.2.0
>
> Attachments: HBASE-13755-v1.patch, HBASE-13755-v2.patch,
> HBASE-13755-v3.patch, HBASE-13755-v3.patch, HBASE-13755-v3.patch,
> HBASE-13755-v3.patch, HBASE-13755-v3.patch, HBASE-13755-v4.patch
>
>
> Followup for HBASE-13375.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
