[
https://issues.apache.org/jira/browse/HBASE-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639272#comment-13639272
]
Ted Yu commented on HBASE-8372:
-------------------------------
bq. we'd now have copy of each value into a new mutableConf
Can you clarify the meaning of 'a new mutableConf' ? Once mutableConf is
materialized inside CompoundConfiguration, the list of ImmutableConfigMap's are
no longer needed.
In patch v5, each time freezeMutableConf() is called, ImmutableConfWrapper
would keep a reference to mutableConf. This leads to more memory consumption.
> 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, hbase-8372.v2.patch,
> hbase-8372.v3.patch, hbase-8372.v4.patch, hbase-8372.v5.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
