[
https://issues.apache.org/jira/browse/HADOOP-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283553#comment-13283553
]
Hudson commented on HADOOP-6871:
--------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #2308 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2308/])
HADOOP-6871. When the value of a configuration key is set to its unresolved
form, it causes an IllegalStateException in Configuration.get() stating that
substitution depth is too large. Contributed by Arvind Prabhakar (harsh)
(Revision 1342626)
Result = FAILURE
harsh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1342626
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
> When the value of a configuration key is set to its unresolved form, it
> causes the IllegalStateException in Configuration.get() stating that
> substitution depth is too large.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-6871
> URL: https://issues.apache.org/jira/browse/HADOOP-6871
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 3.0.0
> Reporter: Arvind Prabhakar
> Fix For: 3.0.0
>
> Attachments: HADOOP-6871-1.patch, HADOOP-6871-2.patch,
> HADOOP-6871-3.patch, HADOOP-6871.patch
>
>
> When a configuration value is set to its unresolved expression string, it
> leads to recursive substitution attempts in
> {{Configuration.substituteVars(String)}} method until the max substitution
> check kicks in and raises an IllegalStateException indicating that the
> substitution depth is too large. For example, the configuration key
> "{{foobar}}" with a value set to "{{$\{foobar\}}}" will cause this behavior.
> While this is not a usual use case, it can happen in build environments where
> a property value is not specified and yet being passed into the test
> mechanism leading to failures due to this limitation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
