You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Ahmed Radwan (JIRA)" <ji...@apache.org> on 2012/09/05 02:07:08 UTC

[jira] [Updated] (HADOOP-8749) HADOOP-8031 changed the way in which relative xincludes are handled in Configuration.

     [ https://issues.apache.org/jira/browse/HADOOP-8749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ahmed Radwan updated HADOOP-8749:
---------------------------------

    Attachment: HADOOP-8749_rev2.patch

Thanks Todd, ATM and Steve!
Here is the updated patch. I have added a test case to cover when a relative path is used in the XInclude.
                
> HADOOP-8031 changed the way in which relative xincludes are handled in Configuration.
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8749
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8749
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Ahmed Radwan
>            Assignee: Ahmed Radwan
>         Attachments: HADOOP-8749.patch, HADOOP-8749_rev2.patch
>
>
> The patch from HADOOP-8031 changed the xml parsing to use DocumentBuilder#parse(InputStream uri.openStream()) instead of DocumentBuilder#parse(String uri.toString()).I looked into the implementation of javax.xml.parsers.DocumentBuilder and org.xml.sax.InputSource and there is a difference when the DocumentBuilder parse(String) method is used versus parse(InputStream).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira