[HADOOP-13802] Make generic options help more consistent, and aligned

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.9.0, 3.0.0-alpha2
• Target Version/s: 3.0.0-alpha2
• Hadoop Flags: Reviewed
• Assignee: Grant Sohn
• Reporter: Grant Sohn
• Created: 07/Nov/16 18:31
• Updated: 16/Nov/16 14:29
• Resolved: 08/Nov/16 23:48

Description

The generic options have always been this:

Generic options supported are
-conf <configuration file>     specify an application configuration file
-D <property=value>            use value for given property
-fs <local|namenode:port>      specify a namenode
-jt <local|resourcemanager:port>    specify a ResourceManager
-files <comma separated list of files>    specify comma separated files to be copied to the map reduce cluster
-libjars <comma separated list of jars>    specify comma separated jar files to include in the classpath.
-archives <comma separated list of archives>    specify comma separated archives to be unarchived on the compute machines.

The general command line syntax is
bin/hadoop command [genericOptions] [commandOptions]

However, almost all the hadoop command help follow an unwritten style which is similar to man page descriptions.
This is the proposed improvement.

Generic options supported are:
-conf <configuration file>     specify an application configuration file
-D <property=value>            define a value for given property
-fs <local|namenode:port>      specify a namenode
-jt <local|jobtracker:port>    specify a job tracker
-files <file1,...>             specify a comma-separated list of files to be copied to the map reduce cluster
-libjars <jar1,...>            specify a comma-separated list of jar files to be included in the classpath
-archives <archive1,...>       specify a comma-separated list of archives to be unarchived on the compute machines

Issue Links

• breaks: MAPREDUCE-6811 TestPipeApplication#testSubmitter fails after HADOOP-13802