[jira] [Resolved] (MAPREDUCE-475) JobConf should validate key names in well-defined namespaces and warn on misspelling

["Allen Wittenauer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-475.
----------------------------------------

    Resolution: Fixed

I'm going to closed this as fixed since Hadoop is much better about notifying users of deprecated options.  There was a lot more discussed here and other jiras opened that take up some of those other topics.

> JobConf should validate key names in well-defined namespaces and warn on misspelling
> ------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-475
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-475
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Aaron Kimball
>            Priority: Minor
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> A discussion on the mailing list reveals that some configuration strings in the JobConf are deprecated over time and new configuration names replace them:
> e.g., "mapred.output.compression.type" is now replaced with "mapred.map.output.compression.type"
> Programmers who have been manually specifying the former string, however, receive no diagnostic output during testing to suggest that their compression type is being silently ignored.
> It would be desirable to notify developers of this change by printing a warning message when deprecated configuration names are used in a newer version of Hadoop. More generally, when any configuration string in the mapred.\*, fs.\*, dfs.\*, etc namespaces are provided by a user and are not recognized by Hadoop, it is desirable to print a warning, to indicate malformed configurations. No warnings should be printed when configuration keys are in user-defined namespaces (e.g., "myprogram.mytask.myvalue").



--
This message was sent by Atlassian JIRA
(v6.2#6252)