hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milind Bhandarkar (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-5404) GenericOptionsParser should parse generic options even if they appear after Tool-specific options
Date Thu, 05 Mar 2009 01:01:56 GMT
GenericOptionsParser should parse generic options even if they appear after Tool-specific options
-------------------------------------------------------------------------------------------------

                 Key: HADOOP-5404
                 URL: https://issues.apache.org/jira/browse/HADOOP-5404
             Project: Hadoop Core
          Issue Type: Improvement
          Components: util
    Affects Versions: 0.19.1
         Environment: All
            Reporter: Milind Bhandarkar


Currently, when GenericOptionsParser encounters an unrecognized option, it stops processing
command-line arguments, and returns the rest to the specific Tool. This forces users to remember
the order of arguments, and leads to errors such as following:

org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option:
-Dmapred.reduce.tasks=4
        at org.apache.commons.cli.Parser.processOption(Parser.java:368)
        at org.apache.commons.cli.Parser.parse(Parser.java:185)
        at org.apache.commons.cli.Parser.parse(Parser.java:70)
        at
MyTool.run(MyTool.java.java:290)
        at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
        at
MyTool.main(MyTool.java:19)

In Hadoop-streaming as well, -D parameters should appear before streaming-specific arguments,
such as -mapper, -reducer etc.

If GenericOptionsParser were to scan the entire command-line, ignoring unrecognized (tool-specific)
options, and returning all unrecognized options back to the tool, this problem would be solved.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message