[
https://issues.apache.org/jira/browse/HBASE-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638550#comment-13638550
]
Jonathan Hsieh commented on HBASE-8372:
---------------------------------------
Will fix typos. Currently running full suites against hadoop1 and hadoop2.
(ran isolated tests prior to posting test).
bq. If I understand this correctly, this also removes the support for
substitutions from data coming from HTD/HCD configuration and metadata...
This has been the case since this method was added (HBASE-5335, to support
dynamic schema change). I haven't changed the semantics of get (all the HTC,
HCD's values added using maps aren't affected -- they couldn't support this
either).
bq. Size implementation is not correct, but it wasn't before, either.
Since this is "semantics preserving", mind if I TODO this with a follow on
jira? I primarily care about resolving HBASE-8347.
> Provide mutability to CompoundConfiguration
> -------------------------------------------
>
> Key: HBASE-8372
> URL: https://issues.apache.org/jira/browse/HBASE-8372
> Project: HBase
> Issue Type: New Feature
> Reporter: Ted Yu
> Assignee: Jonathan Hsieh
> Attachments: hbase-8372.patch
>
>
> In discussion of HBASE-8347, it was proposed that CompoundConfiguration
> should support mutability.
> This can be done by consolidating ImmutableConfigMap's on first modification
> to CompoundConfiguration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
