[
https://issues.apache.org/jira/browse/HADOOP-8358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-8358:
----------------------------
Attachment: HADOOP-8358.patch
This patch is in HADOOP cause its slightly wide/crossproject. Lemme know if I
should split it though.
Changes summary:
* The NodeManager log (from where I noticed this first) showed this cause there
was a hdfs-default.xml config set for this deprecated prop, and its web filter
loaded that up. Cleaned up hdfs-default.xml.
* The old property lookup existed in JspHelper in HDFS. Changed that to use the
new property.
* Cleaned up the usage of constants for this property, via
CommonConfigurationKeys classes instead of its own constant refs.
* Added new prop and default to core-default.xml
> Config-related WARN for dfs.web.ugi can be avoided.
> ---------------------------------------------------
>
> Key: HADOOP-8358
> URL: https://issues.apache.org/jira/browse/HADOOP-8358
> Project: Hadoop Common
> Issue Type: Improvement
> Components: conf
> Affects Versions: 2.0.0
> Reporter: Harsh J
> Priority: Trivial
> Attachments: HADOOP-8358.patch
>
>
> {code}
> 2012-05-04 11:55:13,367 WARN org.apache.hadoop.http.lib.StaticUserWebFilter:
> dfs.web.ugi should not be used. Instead, use hadoop.http.staticuser.user.
> {code}
> Looks easy to fix, and we should avoid using old config params that we
> ourselves deprecated.
--
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
