You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2017/11/22 17:13:01 UTC
[jira] [Created] (HADOOP-15065) Make mapreduce specific
GenericOptionsParser arguments optional
Elek, Marton created HADOOP-15065:
-------------------------------------
Summary: Make mapreduce specific GenericOptionsParser arguments optional
Key: HADOOP-15065
URL: https://issues.apache.org/jira/browse/HADOOP-15065
Project: Hadoop Common
Issue Type: Improvement
Reporter: Elek, Marton
Priority: Minor
org.apache.hadoop.util.GenericOptionsParser is widely used to use common arguments in all the command line applications.
Some of the common arguments are really generic:
{code}
-D <property=value> define a value for a given property
-fs <file:///|hdfs://namenode:port> specify default filesystem URL to use, overrides 'fs.defaultFS' property from configurations.
-libjars <jar1,...> specify a comma-separated list of jar files to be included in the classpath
{code}
But some are mapreduce specific:
{code}
-jt <local|resourcemanager:port> specify a ResourceManager
-archives <archive1,...> specify a comma-separated list of archives to be unarchived on the compute machines
{code}
In the review of HDFS-12588 it was suggested to remove/turn off the mapreduce specific arguments if they are not required (for example in case of starting namenode or datanode).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org