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 "Sanjay Radia (JIRA)" <ji...@apache.org> on 2008/03/10 15:55:46 UTC

[jira] Updated: (HADOOP-2884) Refactor Hadoop package structure and source tree.

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

Sanjay Radia updated HADOOP-2884:
---------------------------------

    Description: 
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.

  was:
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. 
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.


> Refactor Hadoop package structure and source tree.
> --------------------------------------------------
>
>                 Key: HADOOP-2884
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2884
>             Project: Hadoop Core
>          Issue Type: Improvement
>            Reporter: Sanjay Radia
>            Assignee: Sanjay Radia
>            Priority: Minor
>             Fix For: 0.17.0
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.