Mailing-List: contact chukwa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@incubator.apache.org
Message-ID: <120705.468681285793135164.JavaMail.jira@thor>
Date: Wed, 29 Sep 2010 16:45:35 -0400 (EDT)
From: "Ari Rabkin (JIRA)" <jira@apache.org>
To: chukwa-dev@incubator.apache.org
Subject: [jira] Created: (CHUKWA-527) stronger configuration checking
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

stronger configuration checking
-------------------------------

                 Key: CHUKWA-527
                 URL: https://issues.apache.org/jira/browse/CHUKWA-527
             Project: Chukwa
          Issue Type: New Feature
          Components: data collection, documentation
            Reporter: Ari Rabkin
            Assignee: Ari Rabkin


Chukwa has many configuration options, and it's easy to mis-set them.  I'd like to contribute a module for doing stronger static checks of configuration at startup. 

In particular, this will flag and log cases where:
  An option is set in the Chukwa config files that is never read by Chukwa.
  A non-numeric value is used for a numeric parameter, non-boolean value for boolean parameter, etc.

The table of options and types is automatically generated and then human-checked. It should be easy to keep it up to date.
The changes to the Chukwa codebase should be quite modest: one new Jar, and a handful of lines to invoke that Jar on startup.

Does this sound like a thing people would like to see?

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