hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Spiegelberg (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5335) Dynamic Schema Configurations
Date Sat, 04 Feb 2012 02:01:54 GMT

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

Nicolas Spiegelberg commented on HBASE-5335:
--------------------------------------------

My current proposal is to create a derived class off HBaseConfiguration called HBaseTableConfiguration.
 Also, create a HBaseStoreConfiguration derived from HBaseTableConfiguration.  This will allow
us to specify all the normal Config.get() keys on a per-table, per-CF basis without a major
code refactor.  Still need to flush out how this would look in the schema, since you probably
want to distinguish between reserved keywords and "at your own risk" hidden settings.

For config items that we later identify as important, we can create a reserved keyword and
then map it to the old config name.  This will allow us to iterate fast & stabilize without
needing explicit schema migration.
                
> 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

        

Mime
View raw message