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

["stack (Commented) (JIRA)" <ji...@apache.org>]

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

stack commented on HBASE-5335:
------------------------------

Can you make a patch for trunk Nicolas.  Lets get this in.....

Should you doc this new behavior:

{code}
+    if (value == null) {
+      remove(Bytes.toBytes(key));
{code}

Should this be hasReservedKeywords rather than hasAdvancedKeys?

{code}
+      if (!RESERVED_KEYWORDS.contains(k)) {
+        hasAdvancedKeys = true;
{code}

Yeah, whats ADVANCED vs RESERVER_KEYWORDS?


                
> 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.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