[ https://issues.apache.org/jira/browse/HADOOP-16007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721844#comment-16721844 ]
Jason Lowe commented on HADOOP-16007: ------------------------------------- I tracked this behavior change down to HADOOP-15554. I believe the problem stems from Parser#handleInclude parsing the included sub-resource directly into the Configuration {{properties}} member which bypasses the ordering of properties returned by the Parser#parse method. > Order of property settings is incorrect when includes are processed > ------------------------------------------------------------------- > > Key: HADOOP-16007 > URL: https://issues.apache.org/jira/browse/HADOOP-16007 > Project: Hadoop Common > Issue Type: Bug > Components: conf > Affects Versions: 3.2.0, 3.1.1, 3.0.4 > Reporter: Jason Lowe > Priority: Blocker > > If a configuration file contains a setting for a property then later includes > another file that also sets that property to a different value then the > property will be parsed incorrectly. For example, consider the following > configuration file: > {noformat} > <configuration xmlns:xi="http://www.w3.org/2001/XInclude"> > <property> > <name>myprop</name> > <value>val1</value> > </property> > <xi:include href="/some/other/file.xml"/> > </configuration> > {noformat} > with the contents of /some/other/file.xml as: > {noformat} > <property> > <name>myprop</name> > <value>val2</value> > </property> > {noformat} > Parsing this configuration should result in myprop=val2, but it actually > results in myprop=val1. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org