[ 
https://issues.apache.org/jira/browse/HADOOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597230#action_12597230
 ] 

Doug Cutting commented on HADOOP-2916:
--------------------------------------

> What is the current status of this jira?

What are the benefits of these changes alone?  Some related goals I have are:
 - eventually split hdfs and mapred into separate subprojects
 - remove non-user APIs from javadocs

Does this as it stand help these?  Splitting the tree doesn't address the first 
much, since the real issue there is dependencies, not directory structure.  But 
I guess it's a start.

I can see some progress towards the second here too.  Moving the HDFS server 
code into a separate tree means we can more easily exclude it from javadocs.  
But this does not address moving non-user mapred classes from the javadoc, does 
it?

I think I'd prefer issues that more directly address these goals, or to more 
precisely state the goals and benefits of this issue.


> Refactor src structure, but leave package structure along
> ---------------------------------------------------------
>
>                 Key: HADOOP-2916
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2916
>             Project: Hadoop Core
>          Issue Type: Sub-task
>          Components: dfs
>            Reporter: Sanjay Radia
>            Assignee: Raghu Angadi
>         Attachments: convert-patch.sed, convert-patch.sed, HADOOP-2916.patch, 
> svn-commands.sh, svn-commands.sh
>
>
> This Jira proposes that the src structure be split  as below.
>  The package structure remains the same for this Jira. (Package renaming is 
> part of other JIras  such as HADOOP-2885).
> The idea is that the src will be split   BEFORE the package restructuring
> The new proposed src structure is
> src/test - unchanged
> src/java - will no longer exit , its content will be move to one of core, 
> hdfs, or mapred
> src/core - this will contain the core classes that hadoop applications need 
> to link against.
>   It will contain client side libraries of  all fs file systems:  local, 
> hdfs, kfs, etc
>   jar name hadoop_core.jar
>    src/core/org.apache.hadoop.{conf, fs, filechache, io, ipc, log, metrics, 
> net, record, security, tools, util)
>    src/core/org.apache.hadoop.dfs - this will contain only the client side 
> parts of dfs.
>                    HADOOP-2885 will rename package dfs  to package  fs.hdfs 
> src/hdfs/org.apache.hadoop.dfs - this will contain only the server side of 
> hdfs. 
>       HADOOP-2885 will rename package dfs  to package  fs.hdfs later; a 
> compatible dfs.DistributedFileSystem will be left for compatibility/
>    jar name hadoop_hdfs.jar - this jar can be used to launce NNs and DNs etc.
> src/mapred/org.apache.hadoop.mapred.*
>    Initially one jar:  hadoop_mapred.jar
>    Later this may be split into client-side and server-side jars.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to