[
https://issues.apache.org/jira/browse/HADOOP-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549926
]
Owen O'Malley commented on HADOOP-2385:
---------------------------------------
I can see the motivation/frustration for this, but it doesn't work very well
with the Hadoop configuration model, which is very open. In particular, it
would have to be a very inclusive and configurable list, since the same
configuration file is used for map/reduce and hdfs.
I would think that the best tradeoff would be to have a configuration file that
the namenode and datanodes use to say that all attributes under dfs.* can only
be on this list.
> Validate configuration parameters
> ---------------------------------
>
> Key: HADOOP-2385
> URL: https://issues.apache.org/jira/browse/HADOOP-2385
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Robert Chansler
>
> Configuration parameters should be fully validated before name nodes or data
> nodes begin service.
> Required parameters must be present.
> Required and optional parameters must have values of proper type and range.
> Undefined parameters must not be present.
> (I was recently observing some confusion whose root cause was a mis-spelled
> parameter.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
