[
https://issues.apache.org/jira/browse/HBASE-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235602#comment-13235602
]
Nicolas Spiegelberg commented on HBASE-5335:
--------------------------------------------
Working on a port for trunk. 3 items:
1) coprocessors already use the generic KV api to store their info in
HTableDescriptor. would be nice for someone with coprocessor experience to
view it.
2) Because of #1, may want to consider making a separate config map for this
JIRA. this would require changing the persistent data format though :( We
could use the keyword 'CONFIG' instead of 'ADVANCED'?
3) There is currently a bug in the trunk version of online schema change where
HBaseAdmin.getAlterStatus() is not synchronous. This is causing the new
TestFromClientSide3 to fail. Problem does not exist in 89fb :(
> 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, D2247.2.patch, D2247.3.patch,
> D2247.4.patch, D2247.5.patch, D2247.6.patch, D2247.7.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
