[BIGTOP-316] split up hadoop packages into common, hdfs, mapreduce (and yarn)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.4.0
• Component/s: general
• Assignee: Roman Shaposhnik
• Reporter: Roman Shaposhnik
• Created: 22/Dec/11 22:14
• Updated: 21/Jun/13 23:55
• Resolved: 19/Mar/12 20:43

Description

Here are the new names I would like to propose in hadoop-0.23 branch:

• hadoop (for hadoop-common, but since it won't be limited to just the hadoop-common project it is hadoop)
• hadoop-hdfs
• hadoop-yarn
• hadoop-mapreduce
• hadoop-hdfs-namenode
• hadoop-hdfs-secondarynamenode
• hadoop-hdfs-datanode
• hadoop-yarn-resourcemanager
• hadoop-yarn-nodemanager
• hadoop-mapreduce-historyserver
• hadoop-libhdfs
• hadoop-conf-pseudo
• hadoop-docs

given that they look a tad too long, an alternative would be to drop hadoop- prefix and go with
the shorter versions (even though technically all these projects are sub projects of Hadoop):

• hadoop
• hadoop-conf-pseudo
• hadoop-docs
• hdfs
• yarn
• mapreduce
• hdfs-namenode
• hdfs-secondarynamenode
• hdfs-datanode
• yarn-resourcemanager
• yarn-nodemanager
• mapreduce-historyserver
• libhdfs
• hadoop-conf-pseudo
• hadoop-docs

Please leave your opinion on which one is better in the comments section.

P.S. Quick search over at http://pkgs.org revealed no name clashes for both
long and short versions.

Issue Links

• relates to: HADOOP-7939 Improve Hadoop subcomponent integration in Hadoop 0.23