hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Binglin Chang (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3246) Make Task extensible to support modifications of Task or even alternate programming paradigms
Date Tue, 01 Nov 2011 09:10:32 GMT

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

Binglin Chang commented on MAPREDUCE-3246:
------------------------------------------

The extra warnings are deprecation warnings and I can't make them disappear.

org/apache/hadoop/mapred/MapTask.java:[109,36] [deprecation] org.apache.hadoop.mapred.JobConf
in org.apache.hadoop.mapred has been deprecated


                
> Make Task extensible to support modifications of Task or even alternate programming paradigms
> ---------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3246
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3246
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: task
>    Affects Versions: 0.23.0
>            Reporter: Binglin Chang
>            Assignee: Binglin Chang
>         Attachments: MAPREDUCE-3246-extensible-task.patch, MAPREDUCE-3246-extensible-task.v2.patch,
MAPREDUCE-3246-extensible-task.v3.patch
>
>
> One of MRv2's goal is to support alternate programming paradigms, but building a application
using YARN from the bottom is not trivial. In fact most component of MapReduce can be reused,
mostly the scheduler/master side, and we can make changes/extensions only on the task/slave
side, such as native tasks, hash-aggregation style combiner/reducer interfaces.
> The first thing to do I think is to make task/slave side extensible, more specific, the
Task in JvmTask should serialized with class name, not simply a boolean isMap, and make task
class name configurable in JobConf, there maybe other minor changes. By doing so, developers
can at least extends their own MapTask/ReduceTask.
> I just post my initial thoughts here for opinions. If this change is OK, I can submit
a patch, this is just a trivial work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message