hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8749) HADOOP-8031 changed the way in which relative xincludes are handled in Configuration.
Date Fri, 31 Aug 2012 22:59:07 GMT

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

Aaron T. Myers commented on HADOOP-8749:
----------------------------------------

Great investigation, Ahmed. I noticed that this behavior had changed, but from a quick look
couldn't find any obviously relevant changes.
                
> 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
>
>
> 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

Mime
View raw message