[
https://issues.apache.org/jira/browse/HADOOP-12118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604185#comment-14604185
]
Gabor Liptak commented on HADOOP-12118:
---------------------------------------
Considering that current config XML files do not have a schema, "manual"
parsing seems to be a good backward compatibility solution.
Maven publishes their schemas at:
http://maven.apache.org/xsd/
like
http://maven.apache.org/xsd/maven-4.0.0.xsd
Could a similar setup be used?
http://hadoop.apache.org/xsd/
While most of the config files use the
configuration/property/[name/value/description/final]
hierarchy, there is also fair-scheduler.xml
https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-sls/src/main/sample-conf/fair-scheduler.xml
with its own schema.
> Validate xml configuration files with XML Schema
> ------------------------------------------------
>
> Key: HADOOP-12118
> URL: https://issues.apache.org/jira/browse/HADOOP-12118
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Christopher Tubbs
> Attachments: HADOOP-7947.branch-2.1.patch
>
>
> I spent an embarrassingly long time today trying to figure out why the
> following wouldn't work.
> {code}
> <property>
> <key>fs.defaultFS</key>
> <value>hdfs://localhost:9000</value>
> </property>
> {code}
> I just kept getting an error about no authority for {{fs.defaultFS}}, with a
> value of {{file:///}}, which made no sense... because I knew it was there.
> The problem was that the {{core-site.xml}} was parsed entirely without any
> validation. This seems incorrect. The very least that could be done is a
> simple XML Schema validation against an XSD, before parsing. That way, users
> will get immediate failures on common typos and other problems in the xml
> configuration files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
