[
https://issues.apache.org/jira/browse/HBASE-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Shulman updated HBASE-5335:
-------------------------------------
Labels: configuration online_schema_change schema (was: configuration
schema)
> 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, online_schema_change, schema
> Fix For: 0.94.7, 0.95.0
>
> Attachments: ASF.LICENSE.NOT.GRANTED--D2247.1.patch,
> ASF.LICENSE.NOT.GRANTED--D2247.2.patch,
> ASF.LICENSE.NOT.GRANTED--D2247.3.patch,
> ASF.LICENSE.NOT.GRANTED--D2247.4.patch,
> ASF.LICENSE.NOT.GRANTED--D2247.5.patch,
> ASF.LICENSE.NOT.GRANTED--D2247.6.patch,
> ASF.LICENSE.NOT.GRANTED--D2247.7.patch,
> ASF.LICENSE.NOT.GRANTED--D2247.8.patch, HBASE-5335-trunk-2.patch,
> HBASE-5335-trunk-3.patch, HBASE-5335-trunk-3.patch, HBASE-5335-trunk-4.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 was sent by Atlassian JIRA
(v6.1#6144)
