[
https://issues.apache.org/jira/browse/HADOOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577890#action_12577890
]
Doug Cutting commented on HADOOP-2916:
--------------------------------------
The patch looks fine. It does what is proposed. But I still question whether
it is worthwhile to do this independently of HADOOP-2885. Performed as two
steps we break DFS patches twice. This first step is completely automated (in
a script), so it requires no freeze to trunk, and the script will not get
stale. It would be least disruptive if source paths are only changed once.
What is the downside of combining these?
> 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.
