[
https://issues.apache.org/jira/browse/HADOOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577605#action_12577605
]
Sanjay Radia commented on HADOOP-2916:
--------------------------------------
>Why make this change independent of HADOOP-2885? In either case, HADOOP-2885
>will not be implementable as a patch file, but will require direct svn
>>operations to rename files. Both issues will break other existing patch
>files. So why not combine them?
2885 will require that we block other patches from being submitted commits
while 2885 is being completed.
Hence, we would like to finish 2885 in under 2 days.
The idea was break down HADOOP-2885 into smaller parts; this jira (2916) was an
attempt todo that.
Note that this jira has the property that it has no binary changes; in contrast
2885 changes binary due to package renames.
After this jira is completed, HADOOP-2885
- will not require any renames in src/mapred or src/core;
- will change only imports in src/mapred and src/core
-- Patches on src/mapred and src/core will mostly be auto merged
- will require renames within src/hdfs due to the change in package structure
within hdfs.
-- Doug is right in that 2885 will require renames within src/hdfs and hence
we are duplicating those renames.
After this jira, javadoc cleanup of core/mapred can start independent of 2885
(required for 0.17).
Similarly, work on separate jars can also start if desired (not required for
0.17)
Furthermore, there is a small possibility that 2885 might not make in 0.17
while this jira is likely to be completed in 0.17.
> 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
>
>
> 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.
