hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5275) Mapreduce API: TokenCache incompatibility issues with MR1
Date Mon, 03 Jun 2013 20:00:20 GMT

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

Vinod Kumar Vavilapalli commented on MAPREDUCE-5275:
----------------------------------------------------

bq. 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.
I didn't mean java public. I don't see the annotation in branch-1. It is commented in code
- that doesn't mean it is private. Which branch are you seeing?

bq. The real question is why are we re-adding evolving/private methods removed 9 months ago?
We are just comparing 1.x with 2.x and fixing all changes *if possible*.
                
> 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

Mime
View raw message