[MAPREDUCE-303] refactor the mapred package into small pieces

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Assignee: Owen O'Malley
• Reporter: Owen O'Malley
• Created: 28/Jul/06 20:21
• Updated: 16/Jan/12 09:22
• Resolved: 16/Jan/12 09:22

Description

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?