[
https://issues.apache.org/jira/browse/HADOOP-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277107#comment-14277107
]
Kengo Seki commented on HADOOP-7947:
------------------------------------
[~aw], thank you for your comment! And sorry for the late reply.
* In addition to YARN, httpfs also gets HADOOP_CONF_DIR from the shell
environments (via system properties).
So, I think this is not a special case. Other environment variables, like
HADOOP_HOME, HADOOP_JAAS_DEBUG, HADOOP_PREFIX, are also referred from multiple
classes.
I couldn’t find the global (not only for YARN, shared by multiple projects)
constant of HADOOP_CONF_DIR.
* Thank you for your advice. I’ll refer to GenericOptionsParser.
* Currently, it shows error only when XML is not well-formed. I’ll add a
feature to show where is broken.
> 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
> Labels: newbie
> Attachments: HADOOP-7947.001.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)
