[
https://issues.apache.org/jira/browse/HADOOP-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356942#comment-14356942
]
Kengo Seki commented on HADOOP-7947:
------------------------------------
Thank you for your trial and comment, [~aw]!
Help messages are always needed, of course. :)
Let me discuss whether we should use GenericOptionsParser directly or not.
If we use GenericOptionsParser directly, and when we specify a directory as the
argument of -conf option, instantiating GenericOptionsParser will fail because
GenericOptionsParser takes the argument for a path to file and tries to load it.
I’d like to support directory argument for -conf option because your use case
is very reasonable, so I think it is better not to use GenericOptionsParser
directly.
What do you think?
> Validate XMLs if a relevant tool is available, when using scripts
> -----------------------------------------------------------------
>
> Key: HADOOP-7947
> URL: https://issues.apache.org/jira/browse/HADOOP-7947
> Project: Hadoop Common
> Issue Type: Wish
> Components: scripts
> Affects Versions: 2.7.0
> Reporter: Harsh J
> Assignee: Kengo Seki
> Labels: newbie
> Attachments: HADOOP-7947.001.patch, HADOOP-7947.002.patch,
> HADOOP-7947.003.patch
>
>
> Given that we are locked down to using only XML for configuration and most of
> the administrators need to manage it by themselves (unless a tool that
> manages for you is used), it would be good to also validate the provided
> config XML (*-site.xml) files with a tool like {{xmllint}} or maybe Xerces
> somehow, when running a command or (at least) when starting up daemons.
> We should use this only if a relevant tool is available, and optionally be
> silent if the env. requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
