You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Phabricator (Commented) (JIRA)" <ji...@apache.org> on 2012/03/10 02:58:57 UTC

[jira] [Commented] (HBASE-5335) Dynamic Schema Configurations

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

Phabricator commented on HBASE-5335:
------------------------------------

nspiegelberg has commented on the revision "[jira] [HBASE-5335] Dynamic Schema Config".

  This is a first draft to begin the review process.  Have manually verified that the code works, but no unit tests have been made yet.  Also, need to figure out a way to delete a config value from the shell once added in.

REVISION DETAIL
  https://reviews.facebook.net/D2247

                
> 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
>         Attachments: D2247.1.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