[
https://issues.apache.org/jira/browse/HBASE-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227076#comment-13227076
]
Phabricator commented on HBASE-5335:
------------------------------------
nspiegelberg has commented on the revision "[jira] [HBASE-5335] Dynamic Schema
Config".
INLINE COMMENTS
src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java:41 I think this
would introduce a Guava dependency. I just wanted something with concise set
notation for the rough draft. I'll try to use standard Java APIs for a future
iteration since this is client-side.
src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java:531 There is some
special logic in HTD around ROOT & META regions that make unification
nontrivial.
src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java:452 thanks
for the info. I'll remember to look into 92 implementation details of this
when I do a trunk port.
src/main/java/org/apache/hadoop/hbase/util/CompoundConfiguration.java:39 note
that this is a private interface, so it wouldn't appear in javadoc. I should
add some notes here though.
src/main/ruby/hbase/admin.rb:177 you only hit this error if 1 was specified
but the other wasn't.
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
