[
https://issues.apache.org/jira/browse/HADOOP-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292765#comment-14292765
]
Allen Wittenauer commented on HADOOP-11509:
-------------------------------------------
I understand your position and mostly agree. But we have a huge documentation
problem: all of the examples and java help messages, etc, for the entirety of
Hadoop's lifetime have these options in a different order. Since it doesn't
appear that the parser is particularly smart about processing these things in
any particular order, all of these examples break. This likely means real
world code breaks.
At a minimum, I think this patch requires some human-side edits to make sure
everything is in sync with the expected order of the options.
> change parsing sequence in GenericOptionsParser to parse -D parameters first
> ----------------------------------------------------------------------------
>
> Key: HADOOP-11509
> URL: https://issues.apache.org/jira/browse/HADOOP-11509
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Fix For: 2.7.0
>
> Attachments: HADOOP-11509.1.patch, HADOOP-11509.2.patch
>
>
> In GenericOptionsParser, we need to parse -D parameter first. In that case,
> the user input parameter (through -D) can be set into configuration object
> earlier and used to process other parameters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
