You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2009/06/12 01:43:07 UTC
[jira] Commented: (HADOOP-398) refactor the mapred package into
small pieces
[ https://issues.apache.org/jira/browse/HADOOP-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718667#action_12718667 ]
Owen O'Malley commented on HADOOP-398:
--------------------------------------
We should actually do this in our lifetime. How about:
mapreduce.server.{common,jobtracker,tasktracker}
mapreduce.client
mapreduce.common
> refactor the mapred package into small pieces
> ---------------------------------------------
>
> Key: HADOOP-398
> URL: https://issues.apache.org/jira/browse/HADOOP-398
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.4.0
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
> The mapred package has gotten too big, so I propose changing it to split it into parts.
> I propose the following splits:
> org.apache.hadoop.mapred = client API
> org.apache.hadoop.mapred.task = code for task tracker
> org.apache.hadoop.mapred.job = code for job tracker
> org.apache.hadoop.mapred.utils = non public code that is shared between the servers
> Does anyone have any other divisions that would help?
> I would make the classes sent through RPC public classes in the server's package.
> Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.