[
https://issues.apache.org/jira/browse/HADOOP-16007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724070#comment-16724070
]
Jason Lowe commented on HADOOP-16007:
-------------------------------------
This is not quite the same issue as discovered during the RC0 voting period, as
that's HADOOP-15973. Eric and I have been discussing this quite a bit offline,
and he said that rolling back to the commit before HADOOP-15554 did not fix
HADOOP-15973, so they are related but slightly different issues. We _think_
there's a way to fix both of them with the same change, and Eric is actively
working on that. I agree that we should hold the RC for these fixes, as not
loading the intended config settings properly could lead to very bad behavior
depending upon the property which was accidentally, silently dropped after
upgrading.
> 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
> Assignee: Eric Payne
> 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: [email protected]
For additional commands, e-mail: [email protected]
