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 "Daryn Sharp (Commented) (JIRA)" <ji...@apache.org> on 2012/02/15 18:35:00 UTC

[jira] [Commented] (HADOOP-7995) GenericOptionsParser ought to have better options parsing, and not pick only the options in the front

    [ https://issues.apache.org/jira/browse/HADOOP-7995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208602#comment-13208602 ] 

Daryn Sharp commented on HADOOP-7995:
-------------------------------------

Here's a few examples of how conflicts may occur if the generic options can appear anywhere in the cmdline:
* du -D dir
* ln -fs path

@Harsh
Do you feel this is compelling enough to close the jira?
                
> GenericOptionsParser ought to have better options parsing, and not pick only the options in the front
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7995
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7995
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 0.23.0
>            Reporter: Harsh J
>            Priority: Minor
>              Labels: newbie
>
> The ToolRunner provided GenericOptionsParser stops parsing known options when it encounters the first unknown option string in the String[] today.
> Ideally we should have it be more intelligent and sift through the whole array to pick up all opts, and not just the opts that are at the front of the invoked CLI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira