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

Hudson commented on MAPREDUCE-5234:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1429 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1429/])
    MAPREDUCE-5234. Change mapred.TaskReport and mapreduce.TaskReport for 
binary compatibility with mapred in 1.x but incompatible with 0.23.x. 
Contributed by Mayank Bansal. (Revision 1483940)

     Result = FAILURE
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1483940
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/TaskReport.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/TaskReport.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapred/TestJobInfo.java

                
> Signature changes for getTaskId of TaskReport in mapred
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-5234
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5234
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Mayank Bansal
>             Fix For: 2.0.5-beta
>
>         Attachments: MAPREDUCE-5234-trunk-1.patch, 
> MAPREDUCE-5234-trunk-2.patch, MAPREDUCE-5234-trunk-3.patch, 
> MAPREDUCE-5234-trunk-4.patch, MAPREDUCE-5234-trunk-5.patch
>
>
> TaskReport in mapred of MR2 extends TaskReport in mapreduce, and inherits 
> getTaskId, which return TaskID object. in MR1, this function returns String.

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