[
https://issues.apache.org/jira/browse/HADOOP-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528112
]
Doug Cutting commented on HADOOP-1906:
--------------------------------------
Another option would be to generate the warning but still load
mapred-default.xml, for back-compatibility, in 0.15, and not stop loading it
until 0.16. Is there any point in staging things like that?
> JobConf should warn about the existance of obsolete mapred-default.xml.
> -----------------------------------------------------------------------
>
> Key: HADOOP-1906
> URL: https://issues.apache.org/jira/browse/HADOOP-1906
> Project: Hadoop
> Issue Type: Improvement
> Components: conf
> Reporter: Owen O'Malley
> Fix For: 0.15.0
>
>
> Since the mapred-default.xml is ignored after HADOOP-785, we should generate
> a warning when it is present. Otherwise users forget to move the values to
> hadoop-site.xml and get confused when things don't work right.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
