hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ari Rabkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-7036) spellcheck for configuration
Date Mon, 15 Nov 2010 22:52:13 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932245#action_12932245

Ari Rabkin commented on HADOOP-7036:

Actually, as I think a bit more, XML schema isn't quite as powerful as this approach. The
spellchecker tool is able to check constraints like "this option must be a writable local
file", which don't fit into a schema.

> spellcheck for configuration
> ----------------------------
>                 Key: HADOOP-7036
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7036
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: conf
>            Reporter: Ari Rabkin
>            Assignee: Ari Rabkin
>         Attachments: confspellcheck.jar, hadoopSpellcheck.patch
> Hadoop does fairly limited correctness checks of its configuration. I propose a "configuration
spellcheck" that can automatically catch errors, and particularly can catch cases where users
mis-type the name of an option.
> The system works as follows:
> - Use program analysis to extract the set of options supported by each Hadoop version,
annotated when possible with their types into a 'dictionary file'.
> - Distribute these extracted sets, per version.
> - A script that reads a dictionary file, reads the Hadoop config from a specified directory,
and reports deviations. In particular, the system can report when an option is set that Hadoop
will never read or when an invalid value is specified.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message