[
https://issues.apache.org/jira/browse/HBASE-15780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283304#comment-15283304
]
Mikhail Antonov commented on HBASE-15780:
-----------------------------------------
Agree we shouldn't be breaking that and that this code isn't likely to change.
Was more thinking that in general I'd prefer that when new interfaces are
opened up they're first enabled as evolving to live room for improvement, and
then in 1.4 we can cast them in stone? Could add a class comment saying that
thought this interface is evolving we don't expect it to change.
Though I'd be fine with public-stable either...
> Expose AuthUtil as IA.Public
> ----------------------------
>
> Key: HBASE-15780
> URL: https://issues.apache.org/jira/browse/HBASE-15780
> Project: HBase
> Issue Type: New Feature
> Components: API, security
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Critical
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-15780.1.patch
>
>
> Make AuthUtils IA.Public so that we can point it out to folks who want to
> build long-lived services that talk to secure HBase clusters without
> concerning them with Hadoop APIs like UGI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
