[
https://issues.apache.org/jira/browse/MAPREDUCE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved MAPREDUCE-556.
----------------------------------------
Resolution: Fixed
Closing this as fixed, since this is like four refactors ago.
> Refactor Hadoop package structure and source tree.
> --------------------------------------------------
>
> Key: MAPREDUCE-556
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-556
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
>
> This Jira proposes refactoring the Hadoop package structure and source tree
> Goals
> 1. A little finer package structure.
> - Current structure is a little flat
> - Smaller files (name node and data node are way too big)
> 2. The client interfaces and data types sent across the wire should be
> clearly identifiable by the package they sit in. This will help preserving
> app compatibility since it will be very obvious when one breaks
> the interface.
> 3. Split dfs's client and server side jars.
> 4. Move map-reduce into separate src tree (but same SVN repository) along
> with its separate jar.
> 5. The Javadoc for users of Hadoop should not contain the internal
> server-side interfaces/classes
> 6. Fix all compiler warnings
> 7. Fix/minimize findbug warnings
> The top level package structure remains unchanged:
> hadoop.fs
> hadoop.dfs
> hadoop.mapred
> Etc.
> Considered changing hadoop.dfs to hadoop.hdfs but the "h" does not really add
> much since hadoop is already part of the package name; didn't seem worth
> going to
> through the trouble of breaking compatibility.
> Changes will occur internally within the above packages.
> sub-Jira HADOOP-2885 proposes restructuring hadoop.dfs.
> Other Jiras will be filed for restructuring other parts.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
