hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5231) Constructor of DBInputFormat.DBRecordReader in mapred is changed
Date Sat, 01 Jun 2013 13:03:22 GMT

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

Hudson commented on MAPREDUCE-5231:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk #1417 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1417/])
    MAPREDUCE-5231. Bring back a constructor in mapred's DBInputFormat.DBRecordReader for
binary compatibility with 1.x mapred APIs. Contributed by Zhijie Shen. (Revision 1488436)

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

                
> Constructor of DBInputFormat.DBRecordReader in mapred is changed
> ----------------------------------------------------------------
>
>                 Key: MAPREDUCE-5231
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5231
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>             Fix For: 2.1.0-beta
>
>         Attachments: MAPREDUCE-5231.1.patch
>
>
> The constructor of DBInputFormat.DBRecordReader in mapred is changed from MR1 to RM2.
Though MAPREDUCE-716 tried to deal with the API difference. However, if DBInputFormat.DBRecordReader
is extended, the incompatibility around the constructor is still there.

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

Mime
View raw message