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

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

> Let's go ahead and do this on monday next week. Does that sound reasonable to 
> people? 

Next Monday is 5 days before a planned release branch, right?

I'd still rather see this done at the same time as HADOOP-2885, earlier in a 
release cycle.  I see no point in breaking patches twice: if we're going to 
re-organize the codebase, we should do it all at once, rather than dragging out 
the pain.  But, as it appears I am alone in this belief, I will not veto this.

BTW, the description of this issue proposes to change the jar files, but the 
attached patch does not do that: all that it does is re-arrange source code.  
Given the late point in the release cycle, I think this is a wise choice.  
Restructuring the jar files may have substantial impacts, and ought to be done 
in trunk earlier in a release cycle.



> Refactor src structure, but leave package structure alone
> ---------------------------------------------------------
>
>                 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