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 "Arun C Murthy (JIRA)" <ji...@apache.org> on 2010/02/27 04:38:05 UTC

[jira] Updated: (MAPREDUCE-1528) TokenStorage should not be static

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy updated MAPREDUCE-1528:
-------------------------------------

    Attachment: MAPREDUCE-1528_yhadoop20.patch

Summary of changes:

# Renamed TokenStorage to Credentials to better reflect it's utility.
# Added a Credentials to JobConf (and an accessor: JobConf.getCredentials) since it's the only per-job identifier in an MR application for the old apis, added a JobContext.getCredentials for the new, context-objects api.
# Removed as much cruft as possible from TokenCache, without really going overboard - we need to keep TokenCache since it's Hadoop MapReduce specific and I can't really put everything into Credentials as it's in Hadoop Common.


> TokenStorage should not be static
> ---------------------------------
>
>                 Key: MAPREDUCE-1528
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1528
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Owen O'Malley
>         Attachments: MAPREDUCE-1528_yhadoop20.patch
>
>
> Currently, TokenStorage is a singleton. This doesn't work for some use cases, such as Oozie. I think that each Job should have a TokenStorage that is associated it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.