Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 4 Feb 2012 04:45:54 +0000 (UTC)
From: "Lars Hofhansl (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2100929578.10838.1328330754601.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1107944523.10491.1328320553487.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5335) Dynamic Schema Configurations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-5335:
--------------------------------------

We were just discussing here at SFDC to add a generalized way to serialized Configurations into a HTableDescriptor. What you propose is much cleaner than what we had in mind. So +1 :)

Are you planning some kind of classification theme to distinguish config settings that only make sense globally from those that make sense per CF/Table?

Short term I was planning to add the ability to set arbitrary HTableDescriptor value through the shell, I'll hold of on that.
                
> Dynamic Schema Configurations
> -----------------------------
>
>                 Key: HBASE-5335
>                 URL: https://issues.apache.org/jira/browse/HBASE-5335
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Nicolas Spiegelberg
>            Assignee: Nicolas Spiegelberg
>              Labels: configuration, schema
>
> Currently, the ability for a core developer to add per-table & per-CF configuration settings is very heavyweight.  You need to add a reserved keyword all the way up the stack & you have to support this variable long-term if you're going to expose it explicitly to the user.  This has ended up with using Configuration.get() a lot because it is lightweight and you can tweak settings while you're trying to understand system behavior [since there are many config params that may never need to be tuned].  We need to add the ability to put & read arbitrary KV settings in the HBase schema.  Combined with online schema change, this will allow us to safely iterate on configuration settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira