[HADOOP-16007] Order of property settings is incorrect when includes are processed

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Duplicate
• Affects Version/s: 3.2.0, 3.1.1, 3.0.4
• Component/s: conf
• Target Version/s: 3.2.0, 3.0.4, 3.1.2
• Assignee: Eric Payne
• Reporter: Jason Darrell Lowe
• Created: 14/Dec/18 22:35
• Updated: 14/Oct/19 15:37
• Resolved: 20/Dec/18 16:05

Description

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:

<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>

with the contents of /some/other/file.xml as:

     <property>
       <name>myprop</name>
       <value>val2</value>
     </property>

Parsing this configuration should result in myprop=val2, but it actually results in myprop=val1.

Issue Links

• is caused by: HADOOP-15554 Improve JIT performance for Configuration parsing
• is duplicated by: HADOOP-15973 Configuration: Included properties are not cached if resource is a stream