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

Harsh J updated MAPREDUCE-4415:
-------------------------------

    Target Version/s:   (was: 1.2.0)
       Fix Version/s: 1.2.0
        Release Note: Backported new APIs to get a Job object to 1.2.0 from 
2.0.0. Job API static methods Job.getInstance(), Job.getInstance(Configuration) 
and Job.getInstance(Configuration, jobName) are now available across both 
releases to avoid porting pain.  (was: Backported new APIs to get a Job object 
to 1.x from 2.x: Job.getInstance(), Job.getInstance(Configuration) and 
Job.getInstance(Configuration, jobName))
        Hadoop Flags: Reviewed

Committing to branch-1, thanks Tom and Arun!
                
> Backport the Job.getInstance methods from MAPREDUCE-1505 to branch-1
> --------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4415
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4415
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv1
>    Affects Versions: 1.0.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>             Fix For: 1.2.0
>
>         Attachments: MAPREDUCE-4415.patch
>
>
> In 2.x MR, the Job constructors have all been deprecated in favor of 
> Job.getInstance() calls to get a Job object.
> However, these getInstance methods do not appear to be present in the 1.x MR 
> API, and thereby may cause additional pain to users moving from 1.x to 2.x 
> going forward.
> This patch proposes to add in the getInstance style of methods with suitable 
> test coverage for both style of constructors, while not pulling in anything 
> else from MAPREDUCE-1505 (as we lack 'Cluster' in 1.x). As we're not going to 
> be deprecating the regular ctors in a 1.x release, this is not an 
> incompatible change in any way.

--
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

        

Reply via email to