hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bieniosek (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-4875) server can't set username in JobClient.submitJob for jobs submitted on behalf of other users
Date Tue, 16 Dec 2008 02:13:44 GMT
server can't set username in JobClient.submitJob for jobs submitted on behalf of other users
--------------------------------------------------------------------------------------------

                 Key: HADOOP-4875
                 URL: https://issues.apache.org/jira/browse/HADOOP-4875
             Project: Hadoop Core
          Issue Type: Bug
          Components: mapred
    Affects Versions: 0.19.0
            Reporter: Michael Bieniosek


I have a rpc server that sits in front of hadoop and submits mapreduce jobs on behalf of users
(humans).  However, because hadoop gets username information from the unix username of the
submitting process, all my jobs appear to be from the unix account used by the webserver.

I tried to fix it by doing this:

JobConf conf = ...
JobClient client = ...
conf.setUser(username);
client.submitJob(conf);

But that doesn't work because submitJob overwrites the username I wrote with setUser.

Instead, submitJob should only insert a username into the job if it is not in the config already.
 Alternately, the username might be inserted at the time of creation of the JobConf, so that
I have an opportunity to overwrite it, or the JobConf could supply some hook for me to insert
some alternate username.

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


Mime
View raw message