[ 
https://issues.apache.org/jira/browse/MAPREDUCE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved MAPREDUCE-303.
-------------------------------

    Resolution: Not A Problem

Not a problem after we mavenized the trunk.
                
> refactor the mapred package into small pieces
> ---------------------------------------------
>
>                 Key: MAPREDUCE-303
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-303
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            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.
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

        

Reply via email to