[ 
https://issues.apache.org/jira/browse/OOZIE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239841#comment-13239841
 ] 

Virag Kothari commented on OOZIE-780:
-------------------------------------

An issue was identified in Hadoop 5254 where some updates of java6( till update 
2) were not XincludeAware compliant as those updates used xerces2.6. This issue 
can be resolved by using xerces 2.10. This library has been done as part of 
oozie-781.
                
> 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
>
> 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

        

Reply via email to