[ 
https://issues.apache.org/jira/browse/HADOOP-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551883
 ] 

Doug Cutting commented on HADOOP-2385:
--------------------------------------

> I'd prefer if we had a separate configuration class for each component, say 
> NamenodeConfiguration, DatanodeConfiguration, ...

This can be a problem when a configuration is passed between components.  For 
example, if we had an FsConfiguration, RpcConfiguration, etc., then calls from, 
e.g., mapred code to these would require the creation of a new configuration.  
So this only works well for top-level components, when all calls from a 
component are to components that are configured by Configuration.  But it can 
be hard to know when something is top-level, e.g., we'd like to be able to run 
datanode within other daemons.

> That reminds me about one abandoned issue HADOOP-24 - an attempt to make a 
> configuration interface.

Hmm.  It looks like I dropped the ball on that one!  It's not back-compatible, 
since any code that calls 'new Configuration()' would break, and it's missing 
some javadoc, etc.  But it might still be a nice change, although I don't see 
how it would help us here.

> We should also use xml schema for the verification purposes.

I don't see how that would do sufficient type checking any more easily.  Do you?


> 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.

Reply via email to