[
https://issues.apache.org/jira/browse/MAPREDUCE-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203890#comment-13203890
]
Sanjay Radia commented on MAPREDUCE-3825:
-----------------------------------------
> I should clarify how I implemented #1.
Your description has APIs from both #1 and #2. (ie you use a variation of
getDelegationTokens(renewer, credentials)
I am suggesting that one of the two sets is sufficient.
>getDelegationTokens is required to return only one token, then why not call
>getDelegationToken
Good question. If this method is declared in FileSystem then ViewFileSystem
has to implement it and it cannot return single token - it has multiple tokens.
The fact that you will never ever call getDelegationToken on viewFileSystem and
always call getEmbeddedFileSystems() does not matter - ViewFileSystem has to
honor the contract for FileSystem since it extends it.
> 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
> Attachments: MAPREDUCE-3825.patch
>
>
> 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
