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 "Raghu Angadi (JIRA)" <ji...@apache.org> on 2008/03/12 02:10:46 UTC

[jira] Issue Comment Edited: (HADOOP-2916) Refactor src structure, but leave package structure along

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

rangadi edited comment on HADOOP-2916 at 3/11/08 6:10 PM:
---------------------------------------------------------------

svn-commands.sh and patch for build.xml is attached. 
to apply the changes, start with a clean check out of the trunk and run the following
command at top level directory :

{noformat}
$ sh svn-commands.sh
$ patch -p0 < HADOOP-2916.patch
{noformat}

If this fails for any reason, try :
{noformat}
$ svn revert -R src build.xml
$ rm -rf src/core src/mapred src/hdfs
{noformat} and try to run script again.

There are no changes made to any file under src/.

The changes to build.xml could be better if I had more experience with ant. Essentially each instance of 'src/java' need be replaced by three directories : src/core, src/mapred, and src/hdfs. But this can not be done using just a simple property that has these three values concatinated. Please suggest if there is a better way.

      was (Author: rangadi):
    
svn-commands.sh and patch for build.xml is attached. 
How to apply the changes, start with a clean check out of the trunk and run the following
command at top level directory :

{noformat}
$ sh svn-commands.sh
$ patch -p0 < HADOOP-2916.patch
{noformat}

If this fails for any reason, try :
{noformat}
$ svn revert -R src build.xml
$ rm -rf src/core src/mapred src/hdfs
{noformat} and try to run script again.

There are no changes made to any file under src/.

The changes to build.xml could be better if I had more experience with ant. essentially each instance of 'src/java' need be essentially replaced by three directories src/core, src/mapred, and src/hdfs. But this can not be done using just a simple property that has these three values. Please suggest if there is a better way.
  
> 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
>             Fix For: 0.17.0
>
>         Attachments: HADOOP-2916.patch, 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.