You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Binglin Chang (Created) (JIRA)" <ji...@apache.org> on 2011/10/22 11:04:32 UTC
[jira] [Created] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
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
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
[jira] [Commented] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Binglin Chang (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140982#comment-13140982 ]
Binglin Chang commented on MAPREDUCE-3246:
------------------------------------------
Some code just committed(LocalJobRunner) break the build. Make some change to make it comptable with LocalJobRunner
> 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
[jira] [Updated] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Binglin Chang (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Binglin Chang updated MAPREDUCE-3246:
-------------------------------------
Attachment: MAPREDUCE-3246-extensible-task.v2.patch
> 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
>
>
> 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
[jira] [Commented] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Kang Xiao (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157910#comment-13157910 ]
Kang Xiao commented on MAPREDUCE-3246:
--------------------------------------
+1
a good solution for creating lightweight programming paradigms by resuing mapreduce.
a example programming paradigm may be helpful.
> 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
[jira] [Updated] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Binglin Chang (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Binglin Chang updated MAPREDUCE-3246:
-------------------------------------
Attachment: MAPREDUCE-3246-extensible-task.patch
> 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
>
>
> 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
[jira] [Updated] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Binglin Chang (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Binglin Chang updated MAPREDUCE-3246:
-------------------------------------
Assignee: Binglin Chang
Status: Patch Available (was: Open)
Changes:
# JvmTask readFields/write with class name
# Replace Task constructors with parameters to init() methods
# Add jobconf: mapreduce.map.task.class mapreduce.reduce.task.class
> 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
>
>
> 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
[jira] [Commented] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140893#comment-13140893 ]
Hadoop QA commented on MAPREDUCE-3246:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501729/MAPREDUCE-3246-extensible-task.v2.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause tar ant target to fail.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed the unit tests build
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1231//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1231//console
This message is automatically generated.
> 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
>
>
> 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
[jira] [Commented] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140225#comment-13140225 ]
Hadoop QA commented on MAPREDUCE-3246:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501619/MAPREDUCE-3246-extensible-task.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 1712 javac compiler warnings (more than the trunk's current 1706 warnings).
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1221//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1221//console
This message is automatically generated.
> 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
>
>
> 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
[jira] [Commented] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141026#comment-13141026 ]
Hadoop QA commented on MAPREDUCE-3246:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12501742/MAPREDUCE-3246-extensible-task.v3.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 1740 javac compiler warnings (more than the trunk's current 1738 warnings).
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1233//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1233//console
This message is automatically generated.
> 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
[jira] [Updated] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Binglin Chang (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Binglin Chang updated MAPREDUCE-3246:
-------------------------------------
Status: Open (was: Patch Available)
> 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
[jira] [Commented] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Binglin Chang (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (MAPREDUCE-3246) Make Task extensible to support
modifications of Task or even alternate programming paradigms
Posted by "Binglin Chang (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Binglin Chang updated MAPREDUCE-3246:
-------------------------------------
Attachment: MAPREDUCE-3246-extensible-task.v3.patch
> 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