[
https://issues.apache.org/jira/browse/HADOOP-8749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449901#comment-13449901
]
Hudson commented on HADOOP-8749:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #2695 (See
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2695/])
HADOOP-8749. HADOOP-8031 changed the way in which relative xincludes are
handled in Configuration. (ahmed via tucu) (Revision 1381703)
Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1381703
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/conf/Configuration.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/TestConfiguration.java
> 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
> Fix For: 2.2.0-alpha
>
> Attachments: HADOOP-8749.patch, HADOOP-8749_rev2.patch,
> HADOOP-8749_rev3.patch, HADOOP-8749_rev4.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
