[
https://issues.apache.org/jira/browse/HADOOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597268#action_12597268
]
Sanjay Radia commented on HADOOP-2916:
--------------------------------------
As you noted Doug, it is a start towards the two goals.
In the past I considered doing this as a single big bang and but the issue was
finding the right time for it.
When is the best time to do such a disruptive patch? - it is best to do it
around release boundaries when there are very few outstanding patches.
Splitting the Jira was proposed because I felt that it increased the chances of
getting this work through by allowing incremental progress.
This Jira (2916) affects everyone; however, the MR folks are not effected by
the second larger patch (2885).
It also means that this Jira can get through quickly (or so I thought .. see
my next paragraph).
My feeling is the 2885 will not happen for a while - because these has been and
will continue to be push back to find a better time to do it.
In a discussion in a corridor earlier today, Arun and Owen suggested delaying
this and 2885 to a release boundary.
(Yes we should have had that discussion in the jira but it it was impromptu; I
have requested them to comment on this Jira. )
They feel that now is a very bad time because there are two many outstanding
patches and that this Jira is too disruptive in spite of ragu's script!
So even with this smaller patch which has a convenient script there is very
strong push back.
I expect a much bigger push back for the 2885 (Unless I do it over Christmas :-)
So the suggestion is to apply this patch just before the 0.18 feature freeze
(ie the last patch before the feature freeze).
Are folks okay with this?
> 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.
