Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <101246707.1241557417460.JavaMail.jira@brutus>
Date: Tue, 5 May 2009 14:03:37 -0700 (PDT)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5772) Implement a 'refreshable'
 configuration system with right access-controls etc.
In-Reply-To: <324871529.1241546850428.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706195#action_12706195 ] 

Arun C Murthy commented on HADOOP-5772:
---------------------------------------

Sure, alternatively we could use this jira to track just the 'refreshable' part of the configuration alongwith access-control etc.

> Implement a 'refreshable' configuration system with right access-controls etc.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5772
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5772
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: conf
>            Reporter: Arun C Murthy
>
> We have various bits and pieces of code to refresh certain configuration files, various components to restrict access to who can actually refresh the configs etc. 
> I propose we start thinking about a simple system to support this as a first-class citizen in Hadoop Core...

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