You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Virag Kothari (JIRA)" <ji...@apache.org> on 2012/05/13 06:43:18 UTC
[jira] [Updated] (OOZIE-780) XConfiguration parser can't parse XML
file with element
[ https://issues.apache.org/jira/browse/OOZIE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Virag Kothari updated OOZIE-780:
--------------------------------
For the patch committed in trunk with this JIRA ID (also available under the same JIRA ID in Apache ReviewBoard system), I grant license to ASF for inclusion in ASF works (as per the Apache License ยง5)
> XConfiguration parser can't parse XML file with <include> element
> -----------------------------------------------------------------
>
> Key: OOZIE-780
> URL: https://issues.apache.org/jira/browse/OOZIE-780
> Project: Oozie
> Issue Type: Bug
> Reporter: Virag Kothari
> Assignee: Virag Kothari
>
> E.g core-site.xml
> <xi:include href="**/local-superuser-conf.xml"/>
> <property>
> </property>
> If the hadoop configs like core-site.xml has an <include> element along with <property> elements, then Xconfiguration cannot parse it and HadoopAccessorService cannot load it.
> This piece of code in Xconfiguration throws the error:
> if (!"property".equals(prop.getTagName())) {
> throw new IOException("bad conf file: element not <property>");
> }
> This jira proposes to provide functionality to combine xmls by supporting the <include> element
> StackTrace:
> Caused by: java.io.IOException: bad conf file: element not <property>
> at
> org.apache.oozie.util.XConfiguration.parseDocument(XConfiguration.java:287)
> at org.apache.oozie.util.XConfiguration.parse(XConfiguration.java:244)
> at org.apache.oozie.util.XConfiguration.<init>(XConfiguration.java:63)
> at
> org.apache.oozie.service.HadoopAccessorService.loadHadoopConf(HadoopAccessorService.java:152)
> at
> org.apache.oozie.service.HadoopAccessorService.loadHadoopConfigs(HadoopAccessorService.java:175)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira