You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2009/11/05 03:09:32 UTC
[jira] Created: (MAPREDUCE-1183) Serializable job components:
Mapper, Reducer, InputFormat, OutputFormat et al
Serializable job components: Mapper, Reducer, InputFormat, OutputFormat et al
-----------------------------------------------------------------------------
Key: MAPREDUCE-1183
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1183
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: client
Affects Versions: 0.21.0
Reporter: Arun C Murthy
Assignee: Arun C Murthy
Currently the Map-Reduce framework uses Configuration to pass information about the various aspects of a job such as Mapper, Reducer, InputFormat, OutputFormat, OutputCommitter etc. and application developers use org.apache.hadoop.mapreduce.Job.set*Class apis to set them at job-submission time:
{noformat}
Job.setMapperClass(IdentityMapper.class);
Job.setReducerClass(IdentityReducer.class);
Job.setInputFormatClass(TextInputFormat.class);
Job.setOutputFormatClass(TextOutputFormat.class);
...
{noformat}
The proposal is that we move to a model where end-users interact with org.apache.hadoop.mapreduce.Job via actual objects which are then serialized by the framework:
{noformat}
Job.setMapper(new IdentityMapper());
Job.setReducer(new IdentityReducer());
Job.setInputFormat(new TextInputFormat("in"));
Job.setOutputFormat(new TextOutputFormat("out"));
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.