hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8152) Expand public APIs for security library classes
Date Mon, 09 Apr 2012 20:23:17 GMT

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

Aaron T. Myers commented on HADOOP-8152:
----------------------------------------

bq. Even marking something as Public+Evolving has certain implications. I don't know if I'm
comfortable with some of these being marked public. Will the impacted parties understand when
we break them?

I'd like to think that the impacted parties would understand. Perhaps one of the HBase folk
watching this JIRA could comment? Andrew? Todd?

bq. (It is inevitable we're going to change reloginFromKeytab and likely even remove it as
part of reworking UGI.)

Is it also inevitable that maintaining backward compatibility will be impossible? If it is,
then we can still break them. Hence the "Evolving" annotation.

Also, could you point me toward the JIRA discussing reworking UGI? I'm not familiar with it.
                
> Expand public APIs for security library classes
> -----------------------------------------------
>
>                 Key: HADOOP-8152
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8152
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 2.0.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>         Attachments: HADOOP-8152.patch, HADOOP-8152.patch
>
>
> Currently projects like Hive and HBase use UserGroupInformation and SecurityUtil methods.
Both of these classes are marked LimitedPrivate(HDFS,MR) but should probably be marked more
generally public.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message