[
https://issues.apache.org/jira/browse/HBASE-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201351#comment-13201351
]
Nicolas Spiegelberg commented on HBASE-5335:
--------------------------------------------
@Lars: the original idea was to allow users to arbitrarily set KVs in the
HTableDescriptor and HColumnDescriptor, but make it so users know that what
they're doing is not checked. Need some sort of format to distinguish between
reserved keywords and non-reserved (thinking of doing this on the client side).
As a config value becomes more well-known, we can enforce limitations like you
stated.
I'd rather have this evolve by having a handful of users who want to set a
config value, learn over the long-term that this is useful, and incrementally
refactor the code to ease support for that config. I don't want to get into a
spot where we have to do a large refactor to support this feature & do
extensive sanity checking, only to determine that we only need 20% of the
config values.
> 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
