hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmed Radwan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-6871) 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.
Date Fri, 03 Feb 2012 16:51:53 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199848#comment-13199848
] 

Ahmed Radwan commented on HADOOP-6871:
--------------------------------------

Thanks Arvind, I am still unable to apply the latest patch to trunk. Can you please recheck?
                
> 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
>            Reporter: Arvind Prabhakar
>         Attachments: HADOOP-6871-1.patch, HADOOP-6871-2.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

        

Mime
View raw message