hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Spiegelberg (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5335) Dynamic Schema Configurations
Date Wed, 04 Apr 2012 21:07:26 GMT

     [ https://issues.apache.org/jira/browse/HBASE-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Nicolas Spiegelberg updated HBASE-5335:

    Attachment: HBASE-5335-trunk-2.patch

Version 2 of the trunk patch.  Major changes:

1) Use the keyword CONFIG instead of ADVANCED.  This should be a little more straightforward
to understand.
2) Move CompoundConfiguration into the regionserver namespace and make it a package private
class with a private interface audience.  This will prevent other people from using this transitory
class and avoid documentation.

This patch will fail on TestFromClientSide3 until HBASE-5359 is committed.  
> 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, HBASE-5335-trunk-2.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


View raw message