Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 6 Apr 2012 19:53:25 +0000 (UTC)
From: "Hadoop QA (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <82577291.25326.1333742005793.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=13248656#comment-13248656 ] 

Hadoop QA commented on HBASE-5335:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12521717/HBASE-5335-trunk-3.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 20 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1435//console

This message is automatically generated.
                
> 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
>             Fix For: 0.96.0
>
>         Attachments: D2247.1.patch, D2247.2.patch, D2247.3.patch, D2247.4.patch, D2247.5.patch, D2247.6.patch, D2247.7.patch, D2247.8.patch, HBASE-5335-trunk-2.patch, HBASE-5335-trunk-3.patch, HBASE-5335-trunk.patch
>
>
> 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