hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6269) improve JobConf to add option to not share Credentials between jobs.
Date Fri, 08 May 2015 20:51:04 GMT

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

Thomas Graves commented on MAPREDUCE-6269:
------------------------------------------

I think the word "share" here is confusing.  when I read this jira I thought it meant you
weren't using them at all in the new JobConf.  what you are really doing is either making
a copy of them (if share is false) or directly referencing the credentials if another JobConf
was passed in. I would prefer something more like copyCredentials and a better description.
   And honestly I'm not real fond of copyCredentials because it sounds like if thats not true
they aren't forwarded on to the new one at all.  I think it should be something more descriptive
though.  This is a public api so we should make sure its intuitive

Perhaps someone else has a better idea for wording?

> improve JobConf to add option to not share Credentials between jobs.
> --------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6269
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6269
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client
>            Reporter: zhihai xu
>            Assignee: zhihai xu
>              Labels: BB2015-05-RFC
>         Attachments: MAPREDUCE-6269.000.patch
>
>
> Improve JobConf to add constructor to avoid sharing Credentials between jobs.
> By default the Credentials will be shared to keep the backward compatibility.
> We can add a new constructor with a new parameter to decide whether to share Credentials.
Some issues reported in cascading is due to corrupted credentials
> at
> https://github.com/Cascading/cascading/commit/45b33bb864172486ac43782a4d13329312d01c0e
> If we add this support in JobConf, it will benefit all job clients.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message