[
https://issues.apache.org/jira/browse/MAPREDUCE-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673470#comment-13673470
]
Daryn Sharp commented on MAPREDUCE-5275:
----------------------------------------
bq. I just verified again and it IS public in 1.x.
Yes, in 1.x it has the {{public}} keyword, but it's annotated
{{@InterfaceAudience.Private}} and the class is annotated
{{@InterfaceStability.Evolving}}. A method assuming a 1-to-1 fs to token
mapping cannot work with viewfs and 1-to-many.
The real question is why are we re-adding evolving/private methods removed 9
months ago? What broke? Because it's already broken for viewfs, based on
fragile assumptions if not broken in other cases, and soon the whole assumption
changes. It won't be a problem if a retired private api stays retired.
> Mapreduce API: TokenCache incompatibility issues with MR1
> ---------------------------------------------------------
>
> Key: MAPREDUCE-5275
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5275
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Mayank Bansal
> Fix For: 2.1.0-beta
>
> Attachments: MAPREDUCE-5275-trunk-1.patch,
> MAPREDUCE-5275-trunk-2.patch, MAPREDUCE-5275-trunk-3.patch,
> MAPREDUCE-5275-trunk-4.patch
>
>
> There're following incompatibility issues:
> * Token<DelegationTokenIdentifier> getDelegationToken(Credentials, String) is
> removed
> * Credentials loadTokens(String, Configuration) changes to Credentials
> loadTokens(String, JobConf)
--
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