You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2012/11/26 12:58:58 UTC
[jira] [Commented] (HADOOP-8532) [Configuration] Increase or make
variable substitution depth configurable
[ https://issues.apache.org/jira/browse/HADOOP-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503745#comment-13503745 ]
Harsh J commented on HADOOP-8532:
---------------------------------
Thanks Aaron, I'll try to address that.
However, making it configurable may not be a nice/easy thing to do (chicken and egg?). Perhaps we could just raise the limit to a higher value, or get rid of it?
> [Configuration] Increase or make variable substitution depth configurable
> -------------------------------------------------------------------------
>
> Key: HADOOP-8532
> URL: https://issues.apache.org/jira/browse/HADOOP-8532
> Project: Hadoop Common
> Issue Type: Improvement
> Components: conf
> Affects Versions: 2.0.0-alpha
> Reporter: Harsh J
>
> We've had some users recently complain that the default MAX_SUBST hardcode of 20 isn't sufficient for their substitution needs and they wished it were configurable rather than having to roll about with workarounds such as using temporary smaller substitutes and then building the fuller one after it. We should consider raising the default hardcode, or provide a way to make it configurable instead.
> Related: HIVE-2021 changed something similar for their HiveConf classes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira