You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Sanjay Radia (Commented) (JIRA)" <ji...@apache.org> on 2012/02/07 21:31:02 UTC

[jira] [Commented] (MAPREDUCE-3825) Need generalized multi-token filesystem support

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

Sanjay Radia commented on MAPREDUCE-3825:
-----------------------------------------

Note the FileSystem interface was changed specifically to deal with multiple-filesystem file systems like viewfs (ie it returns an arrays of tokens not a single token).
So the question is: what is broken? 
* The fact that the token cache is keyed by file system uri or
* That FileSystem has a method called getDelegationTokens and not a method called getEmbeddedFileSystems().

When we changed from getDelegationToken() to getDelegationTokens() we had dismissed the alternate you are proposing since we  needed a method to get delegation token from a file system anyway.

                
> Need generalized multi-token filesystem support
> -----------------------------------------------
>
>                 Key: MAPREDUCE-3825
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3825
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 0.23.1, 0.24.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>
> This is the counterpart to HADOOP-7967.  The token cache currently tries to assume a filesystem's token service key.  The assumption generally worked while there was a one to one mapping of filesystem to token.  With the advent of multi-token filesystems like viewfs, the token cache will try to use a service key (ie. for viewfs) that will never exist (because it really gets the mounted fs tokens).

--
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