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

Hudson commented on MAPREDUCE-5013:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1351 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1351/])
    MAPREDUCE-5013. mapred.JobStatus compatibility: MR2 missing constructors 
from MR1. Contributed by Sandy Ryza. (Revision 1448602)

     Result = FAILURE
tomwhite : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1448602
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/JobStatus.java

                
> mapred.JobStatus compatibility: MR2 missing constructors from MR1
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-5013
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5013
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>             Fix For: 2.0.4-beta
>
>         Attachments: MAPREDUCE-5013.patch
>
>
> JobStatus is missing the following constructors in MR2 that were present in 
> MR1
>     public org.apache.hadoop.mapred.JobStatus(org.apache.hadoop.mapred.JobID, 
> float, float, float, int);
>     public org.apache.hadoop.mapred.JobStatus(org.apache.hadoop.mapred.JobID, 
> float, float, int);
>     public org.apache.hadoop.mapred.JobStatus(org.apache.hadoop.mapred.JobID, 
> float, float, float, int, org.apache.hadoop.mapred.JobPriority);
>     public org.apache.hadoop.mapred.JobStatus(org.apache.hadoop.mapred.JobID, 
> float, float, float, float, int, org.apache.hadoop.mapred.JobPriority);

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to