hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7522) Abandon support for expanding ${user.name} in configs
Date Sun, 07 Aug 2011 10:54:27 GMT

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

Aaron T. Myers commented on HADOOP-7522:

bq. I suspect the right answer is just changing the defaults to be away from user-specific
values in any of the default config values. I don't see any fundamental harm in setting the
user.name value.

That's certainly valid. There are some other config defaults I'd like to change as well, which
I think would make things easier to configure for a first-time user of Hadoop.

That said, the point still remains that certain parts of Hadoop will not work if the ${user.name}
feature is used in configs, e.g. mapred.local.dir on a secure cluster. In those cases the
option of using ${user.name} at all is misleading. The alternative, obviously, is to find
and fix those parts of Hadoop which break when ${user.name} is expanded, but that seems like
an unfortunate burden for the Hadoop developers to bear in support of a little-used feature.

I don't feel super strongly about this, but my preference would still be to remove support
for it.

> Abandon support for expanding ${user.name} in configs
> -----------------------------------------------------
>                 Key: HADOOP-7522
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7522
>             Project: Hadoop Common
>          Issue Type: Wish
>          Components: conf
>    Affects Versions: 0.23.0
>            Reporter: Aaron T. Myers
> In practice, I find that the presence of ${user.name} in configs is rarely helpful, and
often causes issues.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message