hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-310) Validate configuration parameters
Date Thu, 17 Jul 2014 19:09:05 GMT

    [ https://issues.apache.org/jira/browse/HDFS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065384#comment-14065384
] 

Allen Wittenauer commented on HDFS-310:
---------------------------------------

Ping!

Since this discussion, there have been some changes in how well Hadoop processes configuration
entries.  I don't think this is close-able, but I do think it should be re-opened for discussion.

I've got a simple question:  would it go a long way to have each config entry labeled with
a simple type and if it null was option?  I'm thinking specifically of a day when we have
Hadoop configuration coming from something like LDAP....

> Validate configuration parameters
> ---------------------------------
>
>                 Key: HDFS-310
>                 URL: https://issues.apache.org/jira/browse/HDFS-310
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message