hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Kimball (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-2866) JobConf should validate key names in well-defined namespaces and warn on misspelling
Date Thu, 21 Feb 2008 04:13:43 GMT
JobConf should validate key names in well-defined namespaces and warn on misspelling
------------------------------------------------------------------------------------

                 Key: HADOOP-2866
                 URL: https://issues.apache.org/jira/browse/HADOOP-2866
             Project: Hadoop Core
          Issue Type: Improvement
          Components: mapred
    Affects Versions: 0.16.0
            Reporter: Aaron Kimball
            Priority: Minor
             Fix For: 0.16.1, 0.17.0


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.*, hdfs.*, 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message