[ https://issues.apache.org/jira/browse/HADOOP-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932244#action_12932244
]
Ari Rabkin commented on HADOOP-7036:
------------------------------------
It would be possible to use XML schema to do the enforcement. I opted for this strategy so
I could reuse the spellcheck component for other systems that use non-XML key-value configuration.
The hard part here isn't the enforcement per se, it's automatically extracting the schema
and keeping it up to date for each version. That's the real contribution here; I'm undertaking
to keep those up to date, using program analysis.
> 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.
|