[
https://issues.apache.org/jira/browse/HADOOP-7341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041752#comment-13041752
]
Daryn Sharp commented on HADOOP-7341:
-------------------------------------
Aaron:
I completely agree the parser needs to be changed, but I don't currently have
the time available. My goal here is a very small/quick change to revert how
every FsShell command (except count) to how it used to work. If you're ok with
that, I think another jira should switch the parser.
Todd:
I suppose it comes down to whether hadoop should favor posix or gnu extensions?
{noformat}
$ mkdir a b
$ ls a -l b
a:
total 0
b:
total 0
$ POSIXLY_CORRECT=1 ls a -l b
ls: -l: No such file or directory
a:
b:
{noformat}
I was just planning to restore the prior behavior.
> Fix option parsing in CommandFormat
> -----------------------------------
>
> Key: HADOOP-7341
> URL: https://issues.apache.org/jira/browse/HADOOP-7341
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.23.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
>
> CommandFormat currently allows options in any location within the args. This
> is not the intended behavior for FsShell commands. Prior to the redesign,
> the commands used to expect option processing to stop at the first non-option.
> CommandFormat was an existing class prior the redesign, but it was only used
> by "count" to find the -q flag. All commands were converted to using this
> class, thus inherited the unintended behavior.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
