[
https://issues.apache.org/jira/browse/HADOOP-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532748
]
Doug Cutting commented on HADOOP-1906:
--------------------------------------
> Although I guess it means you don't have to reconfigure immediately to try
> 0.15.
Yes, that's the key point. We generally try to make it so that upgrading
between major releases should require no code changes, provided your code
compiles and runs without warnings in the prior release. So the first step to
removing anything is generating warnings. For API changes, this means they're
deprecated for at least one release cycle before they're removed. Other
changes are harder to know how to handle, but in this case a warning seems most
consistent with this compatibility policy, no?
> 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
> Assignee: Arun C Murthy
> Fix For: 0.15.0
>
> Attachments: HADOOP-1906_1_20071005.patch
>
>
> 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.
