You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Devaraj Das (JIRA)" <ji...@apache.org> on 2010/02/18 22:57:27 UTC

[jira] Created: (MAPREDUCE-1505) Job class should create the rpc client only when needed

Job class should create the rpc client only when needed
-------------------------------------------------------

                 Key: MAPREDUCE-1505
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1505
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: client
    Affects Versions: 0.20.2
            Reporter: Devaraj Das
             Fix For: 0.22.0


It will be good to have the org.apache.hadoop.mapreduce.Cluster create the rpc client object only when needed (when a call to the jobtracker is actually required). org.apache.hadoop.mapreduce.Job constructs the Cluster object internally and in many cases the application that created the Job object really wants to look at the configuration only. It'd help to not have these connections to the jobtracker especially when Job is used in the tasks (for e.g., Pig calls mapreduce.FileInputFormat.setInputPath in the tasks and that requires a Job object to be passed).

In Hadoop 20, the Job object internally creates the JobClient object, and the same argument applies there too.


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