hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Teppo Kurki (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-115) Hadoop should allow the user to use SequentialFileOutputformat as the output format and to choose key/value classes that are different from those for map output.
Date Fri, 07 Apr 2006 16:25:25 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-115?page=all ]

Teppo Kurki updated HADOOP-115:
-------------------------------

    Attachment: hadoop-115_tk.patch

(1) adds JobConf.set/getMapKey/ValueClass
(2) changes in ReduceTask so that the Map phase classes are used in append & sort
(3) explicit key and value class specification in OutputFormat.getRecordWriter so that they
are not automatically pulled out of JobConf

Tests run ok, but I haven't added tests for different Map/Reduce key/value classes.

Owen's suggestion on automatically typing the OutputFormat when the first record is written
would cause changes in fewer classes, but I had this already working...



> Hadoop should allow the user to use SequentialFileOutputformat as the output format and
to choose  key/value classes that are different from those for map output.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: HADOOP-115
>          URL: http://issues.apache.org/jira/browse/HADOOP-115
>      Project: Hadoop
>         Type: Improvement

>   Components: mapred
>     Reporter: Runping Qi
>  Attachments: hadoop-115_tk.patch
>
> When map tasks write intermediate data out, they always use SequencialFile RecordWriter
with key/value classes from the job object.
> When the reducers write the final results out, its output format is obtained from the
job object. By default, it is TextOutputFormat, and no conflicts.
> However, if one wants to use SequencialFileFormat for the final results, then the key/value
classes are also obtained from the job object, the same as the map tasks' output. Now we have
a problem. It is impossible for the map outputs and reducer outputs use different key/value
classes, if one wants the reducers generate outputs in SequentialFileFormat.
> A simple fix would be to add another two attributes to JobConf class: mapOutputLeyClass
and mapOutputValueClass. That allows the user to have different key/value classes for the
intermediate and final outputs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message